Bug 110930

Summary: i915 0000:00:02.0: GPU HANG: ecode 7:1:0xfefffffe, in kwin_x11 [2437], hang on rcs0
Product: DRI Reporter: jshand2013
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: RESOLVED DUPLICATE QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: intel-gfx-bugs, jshand2013
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: BDW i915 features: GPU hang
Attachments:
Description Flags
dmesg
none
glxinfo details
none
journalctl debug.txt
none
inxi information none

Description jshand2013 2019-06-17 23:18:15 UTC

    
Comment 1 jshand2013 2019-06-17 23:19:25 UTC
Created attachment 144575 [details]
dmesg
Comment 2 jshand2013 2019-06-17 23:19:59 UTC
Created attachment 144576 [details]
glxinfo details
Comment 3 jshand2013 2019-06-17 23:48:29 UTC
Created attachment 144577 [details]
journalctl debug.txt
Comment 4 jshand2013 2019-06-18 00:26:34 UTC
Created attachment 144578 [details]
inxi information
Comment 5 Francesco Balestrieri 2019-06-19 10:41:42 UTC
Thanks for the report. Can you also attach the error state (/sys/class/drm/card0/error)

Also, it would be great if you could try to reproduce the error using drm-tip (https://cgit.freedesktop.org/drm-tip) and kernel parameters drm.debug=0x1e log_buf_len=4M, and if the problem persists attach the full dmesg from boot.
Comment 6 Denis 2019-06-19 10:45:09 UTC
according to the hanged app and reporter, I would close this bug as one more duplicate of https://bugs.freedesktop.org/show_bug.cgi?id=110816

Also I would ask reporter to stop spamming with new issues, because apparently all his hangs have the same root cause, and 3 opened issues from him - (hang in X, in chromium and in kwin) - more then enough :)
Comment 7 Lakshmi 2019-06-25 07:51:58 UTC
Closing this as a duplicate of 110816.

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

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.