GPU HANG since package update
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Won't Fix
|
High
|
Unassigned |
Bug Description
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_
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.
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: waitingForEnvir
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.
Jan 31 11:23:20 TP org.gtk.
Jan 31 11:23:20 TP org.kde.
Jan 31 11:23:20 TP org.gtk.
Jan 31 11:23:20 TP org.kde.
Jan 31 11:23:20 TP org.a11y.
Jan 31 11:23:20 TP org.a11y.
Jan 31 11:23:21 TP sddm[847]: QProcess: Destroyed while process ("/usr/
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-
ProcVersionSign
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CurrentDesktop: KDE
Date: Wed Jan 31 17:48:58 2018
HibernationDevice: RESUME=
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=
RelatedPackageV
linux-
linux-
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.
dmi.board.name: 20FES2N100
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.
dmi.chassis.type: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.family: ThinkPad Yoga 260
dmi.product.name: 20FES2N100
dmi.product.
dmi.sys.vendor: LENOVO
This change was made by a bot.