GPU HANG since package update

[P]

Since today, I get occasional crashes freeze-ups of the GUI, followed by a restart of the X server. In syslog, I find entries like the ones below.

The system was running stably before, so this is a new phenomenon... could this be related to the recent kernel updates?

Obviously, this leads to data loss...

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
Jan 31 11:23:20 TP sddm[847]: kwalletd5: Checking for pam module
Jan 31 11:23:20 TP sddm[847]: kwalletd5: Got pam-login param
Jan 31 11:23:20 TP sddm[847]: kwalletd5: Waiting for hash on 14-
Jan 31 11:23:20 TP sddm[847]: kwalletd5: waitingForEnvironment on: 18
Jan 31 11:23:20 TP sddm[847]: kwalletd5: client connected
Jan 31 11:23:20 TP sddm[847]: kwalletd5: client disconnected
Jan 31 11:23:20 TP org.kde.KScreen[1425]: The X11 connection broke (error 1). Did the X11 server die?
Jan 31 11:23:20 TP org.gtk.vfs.Daemon[1425]: A connection to the bus can't be made
Jan 31 11:23:20 TP org.kde.kglobalaccel[1425]: The X11 connection broke (error 1). Did the X11 server die?
Jan 31 11:23:20 TP org.gtk.vfs.Daemon[1425]: A connection to the bus can't be made
Jan 31 11:23:20 TP org.kde.Spectacle[1425]: The X11 connection broke (error 1). Did the X11 server die?
Jan 31 11:23:20 TP org.a11y.atspi.Registry[1558]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
Jan 31 11:23:20 TP org.a11y.atspi.Registry[1558]: after 2218 requests (2218 known processed) with 0 events remaining.
Jan 31 11:23:21 TP sddm[847]: QProcess: Destroyed while process ("/usr/lib/x86_64-linux-gnu/sddm/sddm-helper") is still running.
Jan 31 11:23:21 TP systemd[1]: Stopping User Manager for UID 1000...
Jan 31 11:23:21 TP systemd[1342]: Stopped target Default.
Jan 31 11:23:21 TP systemd[1342]: Stopped target Basic System.
Jan 31 11:23:21 TP systemd[1342]: Stopped target Paths.
Jan 31 11:23:21 TP systemd[1342]: Stopped target Sockets.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-32-generic 4.13.0-32.35
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: pascal 10623 F.... pulseaudio
CurrentDesktop: KDE
Date: Wed Jan 31 17:48:58 2018
HibernationDevice: RESUME=UUID=cb84af7b-bfe3-432a-a69a-6a448b1f667a
InstallationDate: Installed on 2017-12-01 (60 days ago)
InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 138a:0090 Validity Sensors, Inc.
 Bus 001 Device 003: ID 04f2:b531 Chicony Electronics Co., Ltd
 Bus 001 Device 005: ID 056a:5044 Wacom Co., Ltd
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20FES2N100
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=c07aafe2-3841-467a-becb-e8173c55fac4 ro psmouse.synaptics_intertouch=1 nosplash psmouse.synaptics_intertouch=1
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-32-generic N/A
 linux-backports-modules-4.13.0-32-generic N/A
 linux-firmware 1.169.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/30/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: N1GET82W (1.61 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FES2N100
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrN1GET82W(1.61):bd09/30/2017:svnLENOVO:pn20FES2N100:pvrThinkPadYoga260:rvnLENOVO:rn20FES2N100:rvrNotDefined:cvnLENOVO:ct31:cvrNone:
dmi.product.family: ThinkPad Yoga 260
dmi.product.name: 20FES2N100
dmi.product.version: ThinkPad Yoga 260
dmi.sys.vendor: LENOVO

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Does this bug go away if you boot back into the prior kernel version?

[P (pggl)]

I tried to downgrade to an older kernel by removing the newest image, but unfortunately some modules failed to load and I then had only 640x480 resolution (fb). Re-installing the newer kernel image did not fix this. Any advice?

(I know this is not what you asked for, but unfortunately I was faster)

[P (pggl)]

I finally re-installed the system.
Because of another bug (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736017) I have to run 4.15 on this machine.

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

Will report back whether this crash still occurs.

[P (pggl)]

The problem occurs with the new mainline kernel (4.15.0-041500-generic #201802011154 SMP Thu Feb 1 11:55:45 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux). Here are the related dmesg lines:

[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
[

[P (pggl)]

Bug also reported here: https://bugs.freedesktop.org/show_bug.cgi?id=104953

[Daniel van Vugt (vanvugt)]

Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.