Resume from suspend, lock screen causes gpu hang

[James Ferguson]

Frequently, returning from suspend, the lock screen 'crashes'. I typically enter my password, it freezes (sometimes shows me my desktop) and then I get the lock screen again, presumably it's respawned. My syslog shows a kernel stack trace and "drm/i915: Resetting chip after gpu hang"

Just before reporting this it happened twice before I got past the lockscreen to my desktop
----

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-24-generic 4.4.0-24.43
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: james 1988 F.... pulseaudio
CurrentDesktop: Unity
Date: Sun Jun 12 20:58:31 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-05-21 (22 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: LENOVO 2325KZ5
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic root=UUID=72122534-7dd5-411b-9c56-c4844502e0ad ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-24-generic N/A
 linux-backports-modules-4.4.0-24-generic N/A
 linux-firmware 1.157
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/05/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: G2ETA0WW (2.60 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2325KZ5
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: 518896
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrG2ETA0WW(2.60):bd03/05/2013:svnLENOVO:pn2325KZ5:pvrThinkPadX230:rvnLENOVO:rn2325KZ5:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2325KZ5
dmi.product.version: ThinkPad X230
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.7-rc1 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc3-yakkety/

[James Ferguson (james-ferguson)]

Intalled. Will report back with results

$ uname -r
4.7.0-040700rc3-generic

[James Ferguson (james-ferguson)]

Numerous suspend/resumes and no sign of the bug. For reference, I never had this problem on 14.04.

[James Ferguson (james-ferguson)]

(to clarify - I meant no sign of this bug with the 4.7 kernel)

[penalvch (penalvch)]

James Ferguson, the next step is to fully reverse commit bisect from kernel 4.4 to 4.7-rc3 in order to identify the last bad commit, followed immediately by the first good one. Once this good commit has been identified, it may be reviewed for backporting. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

Also, the kernel release names are irrelevant for the purposes of bisecting.

After the fix commit (not kernel version) has been identified, then please mark this report Status Confirmed.

Thank you for your help.

[James Ferguson (james-ferguson)]

since updating to the 4.4.0-28-generic kernel I have not seen this issue. I believe we can declare it fixed. Do we declare it Fix Released, or some other status?

[penalvch (penalvch)]

James Ferguson, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1591790/comments/8 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.