[Bug 87139] [BDW] S3 *ERROR* render ring : timed out trying to stop ring

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Dec 16 21:37:07 PST 2014


https://bugs.freedesktop.org/show_bug.cgi?id=87139

Li Xu <li.l.xu at intel.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|bisect_pending              |
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #2 from Li Xu <li.l.xu at intel.com> ---
The good commit on the next-queued 2014_12_17

commit e2c719b75c8c186deb86570d8466df9e9eff919b
Author: Rob Clark <robdclark at 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 at gmail.com>
    Acked-by: Jani Nikula <jani.nikula at intel.com>
    Signed-off-by: Daniel Vetter <daniel.vetter at ffwll.ch>

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20141217/85063719/attachment.html>


More information about the intel-gfx-bugs mailing list