Bug 93863

Summary: [IVB] Xorg window manager (kwin_x11) crashed after PM sleep resume
Product: DRI Reporter: Lukáš Karas <lukas.karas>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED DUPLICATE QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: intel-gfx-bugs
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: IVB i915 features: GPU hang
Attachments:
Description Flags
zip archive with additional information
none
tail of dmesg log
none
output of glxinfo
none
content of /sys/class/drm/card0/error
none
sudo lspci -vvv -s 00:02.0 none

Description Lukáš Karas 2016-01-25 20:47:17 UTC 
Created attachment 121278 [details]
zip archive with additional information

When I woke-up my laptop, window manager froze. So I execute command `kwin_x11 --replace`. When I inspect kernel log, it contains message that I should fill new bug...

[40791.273813] [drm] GPU HANG: ecode 7:0:0x85fffff8, in kwin_x11 [2614], reason: Ring hung, action: reset


GPU crash log ( /sys/class/drm/card0/error ) and other informations are in attachment:

dmesg.log  (dmesg | tail ...)
glxinfo.log (glxinfo)
gpu-crash-dump.log  ( cat /sys/class/drm/card0/error )
lspci.log ( sudo lspci -vvv -s 00:02.0 )
Comment 1 Lukáš Karas 2016-01-25 20:48:25 UTC 
Created attachment 121279 [details]
tail of dmesg log
Comment 2 Lukáš Karas 2016-01-25 20:48:53 UTC 
Created attachment 121280 [details]
output of glxinfo
Comment 3 Lukáš Karas 2016-01-25 20:49:28 UTC 
Created attachment 121281 [details]
content of /sys/class/drm/card0/error
Comment 4 Lukáš Karas 2016-01-25 20:49:49 UTC 
Created attachment 121282 [details]
sudo lspci -vvv -s 00:02.0
Comment 5 yann 2016-05-20 09:43:31 UTC 
For both bugs:
- Hung happening on "render" ring, 
- Application is "kwin_x11",
- HW/PCI_ID is "0x0166", 
- Instruction/IPETH is "0x7a000003"

*** This bug has been marked as a duplicate of bug 91052 ***

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.