system does not power off after going into hibernation

[b3nmore]

My laptop does not power off anymore after going into hibernation. Instead I have to power off manually by holding the power button for some seconds. Resuming from hibernation does work reliably however.

This is regression, since it works perfectly with the utopic kernel (currently 3.16.0.31.24).

To be more precise, the standard 'platform' mode causes this issue:
echo platform > /sys/power/disk
echo disk > /sys/power/state

When using the 'shutdown' mode the system powers off correctly:
echo shutdown > /sys/power/disk
echo disk > /sys/power/state

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-9-generic 3.19.0-9.9 [modified: boot/vmlinuz-3.19.0-9-generic]
ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
Uname: Linux 3.19.0-9-generic x86_64
ApportVersion: 2.16.2-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: kiran 1458 F.... pulseaudio
CurrentDesktop: XFCE
Date: Sat Mar 14 19:36:16 2015
HibernationDevice: RESUME=UUID=ebcf26a9-f63a-4b55-ad87-31f7b1f3feb6
InstallationDate: Installed on 2015-03-14 (0 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150313)
MachineType: LENOVO 2767WSD
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=f0d3de75-e584-48c4-a3af-7b73dd5eb495 ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-9-generic N/A
 linux-backports-modules-3.19.0-9-generic N/A
 linux-firmware 1.143
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/17/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 7UET94WW (3.24 )
dmi.board.name: 2767WSD
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn2767WSD:pvrThinkPadT400:rvnLENOVO:rn2767WSD:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2767WSD
dmi.product.version: ThinkPad T400
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This change was made by a bot.

[b3nmore (b3nmore)]

While at it, I've tested kernel 4.0-rc3 from mainline and with that one it works again, even in 'platform' mode.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.16 stable 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'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-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/v3.16.7-ckt8-utopic/

[b3nmore (b3nmore)]

> Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.16 stable kernel[0].

Just to clarify: I've reported this bug for the vivid kernel, currently 3.19.0. So I'm not sure, if it helps to test 3.16?

[penalvch (penalvch)]

b3nmore, the next step is to fully reverse commit bisect from kernel 3.19 to 4.0-rc3 in order to identify the last bad commit, followed immediately by the first good one. Once this commit has been identified, then it may be reviewed as a candidate for backporting into your release. 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.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[b3nmore (b3nmore)]

This issue seems to be fixed since the last kernel update from 3.19.0-10 to 3.19.0-12.

While with 3.19.0-10 I can still reproduce it, with 3.19.0-12 it doesn't happen anymore. So for my part it is fixed now.

[penalvch (penalvch)]

b3nmore, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1432222/comments/7 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.