On Wed, Oct 01, 2014 at 11:28:47AM +0200, Daniel Vetter wrote: > This seems to have been accidentally lost in > > commit be62acb4cce1389a28296852737e3917d9cc5b25 > Author: Mika Kuoppala <mika.kuopp...@linux.intel.com> > Date: Fri Aug 30 16:19:28 2013 +0300 > > drm/i915: ban badly behaving contexts > > Without this real gpu hangs only log output at info level, which gets > filtered away by piglit's testrunner. > > v2: Tune down to notice level. Note that we need to add drm/i915 so > that at least the automatic igt dmesg filtering still picks it up. > > v3: git add and lack of coffee don't mix well. > > Cc: Mika Kuoppala <mika.kuopp...@intel.com> > Cc: Chris Wilson <ch...@chris-wilson.co.uk> > Cc: Kenneth Graunke <kenn...@whitecape.org> > Reported-by: Kenneth Graunke <kenn...@whitecape.org> > Signed-off-by: Daniel Vetter <daniel.vet...@intel.com>
Hmm, in my igt hang tests, I don't use dev_priv->gpu_error.stop_rings as it is itself incompatible with the tests. This now causes those to fail with a WARN. -Chris -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
