[Bug 99814] New: GPU Hang after Resume from Hibernation (ecode 8:0:0x00200000)

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Feb 14 16:38:30 UTC 2017


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

            Bug ID: 99814
           Summary: GPU Hang after Resume from Hibernation (ecode
                    8:0:0x00200000)
           Product: DRI
           Version: XOrg git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: kassick at gmail.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

After resuming from hibernation (aka suspend to disk), the GPU always hangs and
get's reset.

When using Xorg, the process caught in the hang is always systemd-logind .
Under Xorg, after the GPU is reset, gnome-shell dies and get's restarted. Xorg
itself does not crash, so no graphical app crashes and the session continues
normally. I have experienced no artifacts afterwards, the system works normally
and hibernate again (to the same results) or suspend to ram (without incident).

When using Wayland, the process caught in the hang is always gnome-shell
itself. After resume, it crashes with the message "intel_do_flush_locked
failed: Input/output error". As shell dies, applications love their connection
to the wayland compositor and the session is eventually finished. Logging again
from GDM works fine and the system can hibernate or suspend, just as under
Xorg.

Suspend-to-ram works without any incident. The gang occurs *only* after
resuming from disk.

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


More information about the intel-gfx-bugs mailing list