pm-hibernate locks up on resume

[teledyn]

hibernate function worked fine with 12.04 and all versions back to 11.04, but with new 12.10, pm-hibernate will put the netbook to sleep, but on resume will light the five Ubuntu-screen dots to red, and then only light two dots to white before it locks up.

this is on a zareason 'teo' netbook which uses the Intel Atom CPU N450
---
ApportVersion: 2.6.1-0ubuntu3
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: garym 5707 F.... pulseaudio
 /dev/snd/pcmC0D0p: garym 5707 F...m pulseaudio
CheckboxSubmission: 2578103fd90166afafd3eb329949e571
CheckboxSystem: 9a6d2af3ffb5e20526ca0ccf9ca2c0bf
DistroRelease: Ubuntu 12.10
HibernationDevice: RESUME=UUID=e40d49f0-2a33-4d45-ac19-b5515277cc31
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 (20100429.4)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-N014
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=fb9924b9-13ca-48bd-9e2e-6145808c8835 ro quiet splash
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-17-generic N/A
 linux-backports-modules-3.5.0-17-generic N/A
 linux-firmware 1.95
Tags: quantal running-unity
Uname: Linux 3.5.0-17-generic i686
UpgradeStatus: Upgraded to quantal on 2012-10-19 (3 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape video
dmi.bios.date: 04/02/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: EN014IG6.10T
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MS-N014
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: MS-N014
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrEN014IG6.10T:bd04/02/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-N014:pvrREV1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-N014:rvrREV1.0:cvnMS-N014:ct10:cvrN/A:
dmi.product.name: MS-N014
dmi.product.version: REV:1.0
dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1069619

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

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

[teledyn (garym-teledyn)]

apport information

[teledyn (garym-teledyn)]

apport information

[teledyn (garym-teledyn)]

apport information

[teledyn (garym-teledyn)]

apport information

[teledyn (garym-teledyn)]

apport information

[teledyn (garym-teledyn)]

apport information

[teledyn (garym-teledyn)]

apport information

[teledyn (garym-teledyn)]

apport information

[teledyn (garym-teledyn)]

apport information

[teledyn (garym-teledyn)]

apport information

[teledyn (garym-teledyn)]

apport information

[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 v3.7 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. Please only remove that one tag and leave the other tags. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

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.7-rc2-raring/

[teledyn (garym-teledyn)]

sounds dangerous. I'll give it a try :)

On Mon, Oct 22, 2012 at 2:14 PM, Joseph Salisbury <
<email address hidden>> wrote:

> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> v3.7 kernel[0] (Not a kernel in the daily directory) and install both
> the linux-image and linux-image-extra .deb packages.
>
> Once you've tested the upstream kernel, please remove the 'needs-
> upstream-testing' tag. Please only remove that one tag and leave the
> other tags. This can be done by clicking on the yellow pencil icon next
> to the tag located at the bottom of the bug description and deleting the
> 'needs-upstream-testing' text.
>
> 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.7-rc2-raring/
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
> ** Tags added: needs-upstream-testing regression-release
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1069619
>
> Title:
> pm-hibernate locks up on resume
>
> Status in “linux” package in Ubuntu:
> Incomplete
>
> Bug description:
> hibernate function worked fine with 12.04 and all versions back to
> 11.04, but with new 12.10, pm-hibernate will put the netbook to sleep,
> but on resume will light the five Ubuntu-screen dots to red, and then
> only light two dots to white before it locks up.
>
> this is on a zareason 'teo' netbook which uses the Intel Atom CPU N450
> ---
> ApportVersion: 2.6.1-0ubuntu3
> Architecture: i386
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: garym 5707 F.... pulseaudio
> /dev/snd/pcmC0D0p: garym 5707 F...m pulseaudio
> CheckboxSubmission: 2578103fd90166afafd3eb329949e571
> CheckboxSystem: 9a6d2af3ffb5e20526ca0ccf9ca2c0bf
> DistroRelease: Ubuntu 12.10
> HibernationDevice: RESUME=UUID=e40d49f0-2a33-4d45-ac19-b5515277cc31
> InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386
> (20100429.4)
> Lsusb:
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-N014
> Package: linux (not installed)
> ProcEnviron:
> TERM=xterm
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ...

[teledyn (garym-teledyn)]

the problem is worse in 3.7.0 030700 rc2, the hibernate goes to sleep as before, but on waking it only gets as far as turning the first white dot to red on the Ubuntu welcome screen and then halts. The last message in syslog reads

PM: Basic memory bitmaps created

on the plus side, the hibernation itself happens much faster on 3.7

Since this is an upgraded machine, I was also able to test on 3.4.0-5 #11 -- I was in 3.4, did the sudo pm-hibernate, it compresses and (slowly) saves the states, on awake the dots turn red and white in sequence and the system comes up in 3.7.0 but not with the saved state, it comes up as a fresh boot (because the kernels mismatch?)

[teledyn (garym-teledyn)]

Did a fresh re-install from a USB stick, and now the pm-hibernate does not hang, but it does not work either -- the system will go into hibernation after saving state, but on resume the system comes back up with a fresh boot; I see PM messages in the syslog but nothing that really stands out as a failure notice (let me know if I can grep for something pertinent)

I then upgraded the kernel image + extras to 3.7.0 as above, I get some fast messages about "cannot add device" and on wake, once again, a fresh session.

this may be significant: although my lock rules are set to lock the screen when the screen blanks, it does not, touching any key resumes the session (normally a wake from hibernate would take me to a screenlock login, but this takes me to a session login) -- Ctrl-Alt-L does blank and lock the screen as expected

I also get frequent errors to report problems that I think fail because apportcheckresume trips an 'internal error' message. I then get a message to say that because I am running a mainline kernel it would be better to report this bug to kernel.org

Thinking that perhaps I still had lib conflicts due to the upgrade, I tried booting to the live test session on the USB and while I can't test hibernate with that, it did still give me frequent internal error messages, so it could be my hardware just isn't 12.10 able -- I can hang in here a few more days perhaps, but I'm thinking I may need to revert to 12.04 to have a useful device :(

[teledyn (garym-teledyn)]

 just a short update of my further prodding -- in dmesg I don't even see it trying to resume from a saved image, and in fact I see it doing recovery operations on the ext4 filesystem as if it had been improperly shutdown, so perhaps it isn't the wake that is broken but the hibernation itself? Is there some way to test this?

I do see one dmesg boot message:

PM: Hibernation image not present or could not be loaded

I don't see anything in particular during the kernel shutdown messages, but then I'm not sure what I should be searching for.

Since I have done a lot of package updates, should I re-run apport-collect 1069619?

[teledyn (garym-teledyn)]

this may not have been a good thing: I installed https://launchpad.net/ubuntu/quantal/i386/hibernate and ran "sudo hibernate" which then, unlike before, looks more like the old hibernate from 12.04 in that it reports compressing an image and takes a little longer to run, which further suggests the prior upgraded installation was not actually saving anything.

but now the system does not boot, it gets to the Ubuntu screen and it continues to cycle red and white dots :(

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]