[Bug 96878] [Bisected: cc2d0e6][HSW] "GPU HANG" msg after autologin to gnome-session

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sun Jul 10 12:29:25 UTC 2016


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

--- Comment #4 from Arek Ruśniak <arek.rusi at gmail.com> ---
I was wrong autologin is not the trigger, the problem is gnome-shell only i
belive. 
I've removed radeon card (radeonsi module causes X crash and this is why
autologin fail)
I disabled gdm service at all and started gnome-session from tty by xinit
script. 

dmesg output for intel only system:

[   32.537198] [drm] stuck on render ring
[   32.537922] [drm] GPU HANG: ecode 7:0:0x85dfbff9, in gnome-shell [562],
reason: Engine(s) hung, action: reset
[   32.537923] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[   32.537923] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[   32.537924] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[   32.537924] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[   32.537925] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[   32.539993] drm/i915: Resetting chip after gpu hang
[   42.570515] [drm] stuck on render ring
[   42.571591] [drm] GPU HANG: ecode 7:0:0x86d2bff9, in gnome-shell [562],
reason: Engine(s) hung, action: reset
[   42.573774] drm/i915: Resetting chip after gpu hang
[   52.570434] [drm] stuck on render ring
[   52.571521] [drm] GPU HANG: ecode 7:0:0x85dfbff9, in Xorg [517], reason:
Engine(s) hung, action: reset
[   52.573678] drm/i915: Resetting chip after gpu hang

I found funny thing, when I run&quit weston session before startx everything
looks normal, no hang, no crash. 

If new crash dump is needed just tell me.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20160710/d5bcb240/attachment.html>


More information about the intel-3d-bugs mailing list