[Bug 105486] New: GPU HANG: ecode 9:0:0x85dffffb, in Xorg [1068], reason: Hang on rcs0, action: reset

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 105486
           Summary: GPU HANG: ecode 9:0:0x85dffffb, in Xorg [1068],
                    reason: Hang on rcs0, action: reset
           Product: DRI
           Version: XOrg git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: bruno.cudini+freedesktop at probesys.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

My X server crashes occasionally, with no reproducible activities.  Here is
what I found in the /var/log/messages:

Mar 13 11:44:00 cannes kernel: [drm] GPU HANG: ecode 9:0:0x85dffffb, in Xorg
[1068], reason: Hang on rcs0, action: reset
Mar 13 11:44:00 cannes kernel: [drm] GPU hangs can indicate a bug anywhere in
the entire gfx stack, including userspace.
Mar 13 11:44:00 cannes kernel: [drm] Please file a _new_ bug report on
bugs.freedesktop.org against DRI -> DRM/Intel
Mar 13 11:44:00 cannes kernel: [drm] drm/i915 developers can then reassign to
the right component if it's not a kernel issue.
Mar 13 11:44:00 cannes kernel: [drm] The gpu crash dump is required to analyze
gpu hangs, so please always attach it.
Mar 13 11:44:00 cannes kernel: [drm] GPU crash dump saved to
/sys/class/drm/card0/error
Mar 13 11:44:00 cannes kernel: i915 0000:00:02.0: Resetting rcs0 after gpu hang
Mar 13 11:44:08 cannes kernel: i915 0000:00:02.0: Resetting rcs0 after gpu hang
Mar 13 11:44:16 cannes kernel: i915 0000:00:02.0: Resetting rcs0 after gpu hang
Mar 13 11:44:24 cannes kernel: i915 0000:00:02.0: Resetting rcs0 after gpu hang
Mar 13 11:44:32 cannes kernel: i915 0000:00:02.0: Resetting rcs0 after gpu hang 
Mar 13 11:44:33 cannes journal[5403]: xdg-desktop-portal-gtk: Fatal IO error 11
(Resource temporarily unavailable) on X server :0.
Mar 13 11:44:33 cannes at-spi-bus-launcher[2217]: XIO:  fatal IO error 11
(Resource temporarily unavailable) on X server ":0"
Mar 13 11:44:33 cannes at-spi-bus-launcher[2217]:      after 134897 requests
(134897 known processed) with 0 events remaining.
Mar 13 11:44:34 cannes journal[2514]: cinnamon-screensaver-main.py: Fatal IO
error 11 (Resource temporarily unavailable) on X server :0.
Mar 13 11:44:34 cannes kdm[1049]: X server for display :0 terminated
unexpectedly
Mar 13 11:44:34 cannes systemd[1799]: xdg-desktop-portal-gtk.service: Main
process exited, code=exited, status=1/FAILURE
Mar 13 11:44:34 cannes kernel: show_signal_msg: 3 callbacks suppressed
Mar 13 11:44:34 cannes kernel: SHCLIP[6438]: segfault at 5815b590 ip
00007fe21fa46f05 sp 00007fe116022a30 error 4 in
libc-2.25.so[7fe21fa0c000+1cb000]
Mar 13 11:44:34 cannes audit[6088]: ANOM_ABEND auid=2053 uid=2053 gid=2001
ses=1 pid=6088 comm="SHCLIP" exe="/usr/lib64/virtualbox/VirtualBox" sig=11
res=1
Mar 13 11:44:35 cannes systemd[1799]: xdg-desktop-portal-gtk.service: Unit
entered failed state.
Mar 13 11:44:35 cannes systemd[1799]: xdg-desktop-portal-gtk.service: Failed
with result 'exit-code'.
Mar 13 11:44:35 cannes python3[20342]: The X11 connection broke (error 1). Did
the X11 server die?

-- 
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/20180313/78fca476/attachment.html>