Bug 104953

Summary: [skl] GPU HANG: ecode 9:0:0x85dffffb, in Xorg
Product: Mesa Reporter: PN <pascal.ggl>
Component: Drivers/DRI/i965Assignee: Intel 3D Bugs Mailing List <intel-3d-bugs>
Status: RESOLVED MOVED QA Contact: Intel 3D Bugs Mailing List <intel-3d-bugs>
Severity: blocker    
Priority: medium CC: intel-gfx-bugs, kai.heng.feng, pascal.ggl
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: Content of /sys/class/drm/card0/error

Description PN 2018-02-05 18:25:46 UTC
Created attachment 137172 [details]
Content of /sys/class/drm/card0/error

About a week ago, my system froze for the first time with the following syslog entries:

Jan 31 11:22:42 TP kernel: [14282.025287] [drm] GPU HANG: ecode 9:0:0x86dffffd, in Xorg [870], reason: Hang on rcs0, action: reset
Jan 31 11:22:42 TP kernel: [14282.025322] drm/i915: Resetting chip after gpu hang
Jan 31 11:22:42 TP kernel: [14282.025486] [drm] RC6 on
Jan 31 11:22:46 TP kernel: [14285.246630] asynchronous wait on fence i915:kwin_x11[1506]/1:bd84 timed out
Jan 31 11:22:50 TP kernel: [14290.046737] drm/i915: Resetting chip after gpu hang
Jan 31 11:22:50 TP kernel: [14290.046964] [drm] RC6 on
Jan 31 11:23:03 TP kernel: [14303.006629] drm/i915: Resetting chip after gpu hang
Jan 31 11:23:03 TP kernel: [14303.006806] [drm] RC6 on
Jan 31 11:23:11 TP kernel: [14311.006544] drm/i915: Resetting chip after gpu hang
Jan 31 11:23:11 TP kernel: [14311.006715] [drm] RC6 on
Jan 31 11:23:19 TP kernel: [14319.006432] drm/i915: Resetting chip after gpu hang
Jan 31 11:23:19 TP kernel: [14319.006606] [drm] RC6 on
Jan 31 11:23:20 TP org.kde.kuiserver[1425]: kuiserver: Fatal IO error: client killed

The kernel back then was: Linux 4.13.0-32-generic x86_64

This occurred several times a day. I reported this bug here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746551

I then re-installed kubuntu 17.10, plus a newer 4.15 mainline kernel, but the crash happened again:

Linux kernel:

Linux 4.15.0-041500-generic #201802011154 SMP Thu Feb 1 11:55:45 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Dmesg entries:

[16127.462805] [drm] GPU HANG: ecode 9:0:0x85dffffb, in Xorg [887], reason: Hang on rcs0, action: reset
[16127.462806] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[16127.462807] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[16127.462807] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[16127.462807] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[16127.462808] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[16127.462813] i915 0000:00:02.0: Resetting rcs0 after gpu hang
[16135.453438] i915 0000:00:02.0: Resetting rcs0 after gpu hang
[16143.452952] i915 0000:00:02.0: Resetting rcs0 after gpu hang
[16157.468290] i915 0000:00:02.0: Resetting rcs0 after gpu hang
[16171.451587] i915 0000:00:02.0: Resetting rcs0 after gpu hang

The content of /sys/class/drm/card0/error is attached as requested
Comment 1 PN 2018-02-05 20:20:58 UTC
Also occurs booting into 4.13.0-21-generic
Comment 2 Mark Janes 2018-02-05 23:32:33 UTC
Please install the oibaf ppa and see if latest mesa fixes the issue.
Comment 3 PN 2018-02-07 07:18:09 UTC
I installed these but after an apt-get upgrade yesterday the system does not boot to the login screen and I do not have any network anymore...  

Also, before the fatal upgrade the colors seemed not to be right, and some drop-down menus did not work in Firefox.
Comment 4 GitLab Migration User 2019-09-25 19:08:26 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1685.

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.