Regression: Suspend broken on Thinkpad P50 with 4.8.0-32-generic

[Guillaume Martres]

Suspending to ram and to disk works perfectly fine on the 4.8.0-30-generic kernel. On 4.8.0-32-generic it works some of the time, but most of the time it freezes the machine. When the machine is frozen the screen is turned off, the power button light is on, but the machine does not respond to any input including the Magic SysRq keys, the only thing that can be done is powering off the machine by pressing the power button for 10 seconds. This happens both with suspend-to-ram and suspend-to-disk.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-32-generic 4.8.0-32.34
ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
Uname: Linux 4.8.0-32-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: smarter 1803 F.... pulseaudio
CurrentDesktop: KDE
Date: Mon Jan 9 16:42:48 2017
HibernationDevice: RESUME=UUID=a1a154db-3fbe-43e4-92d1-987022206599
InstallationDate: Installed on 2012-09-28 (1563 days ago)
InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120928)
MachineType: LENOVO 20ENCTO1WW
ProcFB:
 0 nouveaufb
 1 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-32-generic root=UUID=bf5c18a6-40c4-4768-82bc-5c47a1324be5 ro ipv6.disable=1 i915.enable_psr=0
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-32-generic N/A
 linux-backports-modules-4.8.0-32-generic N/A
 linux-firmware 1.161.1
SourcePackage: linux
UpgradeStatus: Upgraded to yakkety on 2016-04-15 (269 days ago)
dmi.bios.date: 08/03/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: N1EET57W (1.30 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20ENCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrN1EET57W(1.30):bd08/03/2016:svnLENOVO:pn20ENCTO1WW:pvrThinkPadP50:rvnLENOVO:rn20ENCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20ENCTO1WW
dmi.product.version: ThinkPad P50
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.10 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.10-rc3

[Guillaume Martres (smarter)]

The bug does not appear in 4.10-rc3

[Guillaume Martres (smarter)]

Kernel 4.8.0-32 introduced changes from the mainline kernels 4.8.7, 4.8.8, 4.8.9, 4.8.10 and 4.8.11 . In my testing, 4.8.8 works fine and suspend is broken starting with 4.8.9. Furthermore, suspend is still broken with the latest 4.8 kernel which is 4.8.17 (therefore the tag kernel-fixed-upstream might not be appropriate).

Do you have any kind of infrastructure to find regressions in kernels? For example, something that would automatically build kernels for every commit between 4.8.8 and 4.8.9 so that I can try to find the culprit by bisection?

[Guillaume Martres (smarter)]

Bug reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=192471

[Guillaume Martres (smarter)]

Bug closed upstream since 4.8 is EOL and the bug does not appear in 4.9 and 4.10. I'm willing to do a bisect to find the problematic commit, but only if I can get some guarantee that this will lead to someone taking the time to review the result and do what's needed to get a fix in 16.10. Otherwise I'm personally fine running a mainline kernel.

[Andy Whitcroft (apw)]

This bug was nominated against a series that is no longer supported, ie yakkety. The bug task representing the yakkety nomination is being closed as Won't Fix.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.