Created attachment 110604 [details] dmesg System Environment: -------------------------- Regression: Yes good commit:(drm-intel-next-queued) commit 0b5492d6b53251acab99b1906a328fac56e08be3 Author: Mika Kuoppala <mika.kuoppala@linux.intel.com> Date: Thu Nov 6 13:03:46 2014 +0200 drm/i915: Add gen to the gpu hang ecode for the Brothers in Triage Signed-off-by: Mika Kuoppala <mika.kuoppala@intel.com> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch> Platform: BDW-U BDW-H Kernel: -------------------------- (drm-intel-nightly) latest 41199e9303667a2676d8b79ea5ae7fc6ae3a73fb(fail) (drm-intel-next-queued)latest d299cce76e001406df40c4ff712b33fccbce1222(fail) Bug detailed description: ----------------------------- Error message render ring : timed out trying to stop ring after S3. Steps: --------------------------- Boot up echo mem >/sys/power/state power on
Test on the nightly latest 2014_12_17,error message has disappeared.
The good commit on the next-queued 2014_12_17 commit e2c719b75c8c186deb86570d8466df9e9eff919b Author: Rob Clark <robdclark@gmail.com> Date: Mon Dec 15 13:56:32 2014 -0500 drm/i915: tame the chattermouth (v2) Many distro's have mechanism in place to collect and automatically file bugs for failed WARN()s. And since i915 has a lot of hw state sanity checks which result in WARN(), it generates quite a lot of noise which is somewhat disconcerting to the end user. Separate out the internal hw-is-in-the-state-I-expected checks into I915_STATE_WARN()s and allow configuration via i915.verbose_checks module param about whether this will generate a full blown stacktrace or just DRM_ERROR(). The new moduleparam defaults to true, so by default there is no change in behavior. And even when disabled, you will still get an error message logged. v2: paint the macro names blue, clarify that the default behavior remains the same as before Signed-off-by: Rob Clark <robdclark@gmail.com> Acked-by: Jani Nikula <jani.nikula@intel.com> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Closing old verified.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.