Summary: | [drm] GPU HANG: ecode 9:0:0x85dfbfff, in gnome-shell [10783], reason: Ring hung, action: reset | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | brian.chapman1 | ||||||||
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||
Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||
Severity: | critical | ||||||||||
Priority: | medium | CC: | intel-gfx-bugs, jozef.chudy | ||||||||
Version: | XOrg git | ||||||||||
Hardware: | Other | ||||||||||
OS: | Linux (All) | ||||||||||
Whiteboard: | |||||||||||
i915 platform: | SKL | i915 features: | GPU hang | ||||||||
Attachments: |
|
Description
brian.chapman1
2016-09-20 01:24:03 UTC
Can you attach gpu crash dump located at /sys/class/drm/card0/error ? Created attachment 126680 [details] /var/spool/abrt/oops-date/backtrace Error file was empty, but I've attached other files. I've also installed http://elrepo.org/linux/kernel/el7/x86_64/RPMS/kernel-ml-4.7.4-1.el7.elrepo.x86_64.rpm and things have been more stable. Thanks Created attachment 126681 [details]
/var/spool/abrt/oops-date/dmesg
(In reply to brian.chapman1 from comment #2) > Error file was empty, but I've attached other files. Did you try to cp the file, or did you just look at the size? The file in debugfs is generated on the fly, so the fs reports 0 size. Created attachment 127049 [details]
dmesg_error
/sys/class/drm/card0/error not present 0kb in size
(In reply to yann from comment #1) > Can you attach gpu crash dump located at /sys/class/drm/card0/error ? There is no error log in path mentioned (In reply to Jozef Chudy from comment #6) > (In reply to yann from comment #1) > > Can you attach gpu crash dump located at /sys/class/drm/card0/error ? > > There is no error log in path mentioned 0 kb is expected because this dump is done dynamically. So execute "cat /sys/class/drm/card0/error | gzip > error.gz" and you should get it :) tried .... erro.gz got created with "no error state collected" within (In reply to Jozef Chudy from comment #8) > tried .... erro.gz got created with "no error state collected" within I would recommend to update your kernel and mesa to latest versions, to allow you benefit of all work done on GPU recovery code and re-test. In parallel, please attached non truncated kernel log (starting from boot up to gpu hang message). Brian maybe you miss the last comment on your bug, but please review Yann's last comment and reply if the problem exist with newest confirguration (kernel/mesa) update with logs and set the bug to reopen if the problem is not there anymore please set the bug to resolved if no action is taken in 30 days the bug will be closed due to lack of activity Timeout - assuming to be fixed. If problem still persist on the latest kernels (preferable drm-tip from git://anongit.freedesktop.org/git/drm-tip), please change status to REOPENED and attach proper details (see https://01.org/linuxgraphics/documentation/how-report-bugs) and describe the use case your exercised ending up the failure. |
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.