hibernate fails (immediate thaw)

[Alex Nastetsky]

Attempting to hibernate fails. Looking at the dmesg log, it immediately starts thawing after hibernating. Relevant parts of the log are below (full log is attached). Note that I have no problems suspending/resuming to RAM.

[ 1617.111123] ACPI: Preparing to enter system sleep state S4
[ 1617.191752] PM: Saving platform NVS memory
[ 1617.214333] Disabling non-boot CPUs ...
[ 1617.214357] CPU0 attaching NULL sched-domain.
[ 1617.214361] CPU1 attaching NULL sched-domain.
[ 1617.214364] CPU2 attaching NULL sched-domain.
[ 1617.214367] CPU3 attaching NULL sched-domain.
[ 1617.214370] CPU4 attaching NULL sched-domain.
[ 1617.214373] CPU5 attaching NULL sched-domain.
[ 1617.214376] CPU6 attaching NULL sched-domain.
[ 1617.214379] CPU7 attaching NULL sched-domain.
[ 1617.278247] CPU0 attaching NULL sched-domain.
[ 1617.279455] Breaking affinity for irq 25
[ 1617.280575] CPU 1 is now offline
[ 1617.282407] Breaking affinity for irq 26
[ 1617.283516] CPU 2 is now offline
[ 1617.285267] Breaking affinity for irq 27
[ 1617.286380] CPU 3 is now offline
[ 1617.288119] Breaking affinity for irq 28
[ 1617.289217] CPU 4 is now offline
[ 1617.290986] Breaking affinity for irq 12
[ 1617.291013] Breaking affinity for irq 23
[ 1617.292089] CPU 5 is now offline
[ 1617.293578] Breaking affinity for irq 1
[ 1617.293617] Breaking affinity for irq 17
[ 1617.294713] CPU 6 is now offline
[ 1617.296237] Breaking affinity for irq 9
[ 1617.296259] Breaking affinity for irq 16
[ 1617.397336] CPU 7 is now offline
[ 1617.397338] SMP alternatives: switching to UP code
[ 1617.403294] Extended CMOS year: 2000
[ 1617.403381] PM: Creating hibernation image:
[ 1617.523005] PM: Need to copy 125533 pages
[ 1617.523008] PM: Normal pages needed: 36996 + 1024, available pages: 190642
[ 1617.867600] PM: Hibernation image created (125533 pages copied)
[ 1617.868366] CPU0: Thermal monitoring enabled (TM1)
[ 1617.868431] Extended CMOS year: 2000
[ 1617.868491] Enabling non-boot CPUs ...
[ 1617.868645] SMP alternatives: switching to SMP code
[ 1617.874210] Booting processor 1 APIC 0x2 ip 0x6000
[ 1617.884369] Initializing CPU#1

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-24-generic-pae 2.6.32-24.38
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-24.38-generic-pae 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic-pae i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: alex 1711 F.... pulseaudio
 /dev/snd/pcmC0D0p: alex 1711 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xd6600000 irq 22'
   Mixer name : 'Realtek ALC269'
   Components : 'HDA:10ec0269,104313d3,00100004'
   Controls : 18
   Simple ctrls : 10
Card1.Amixer.info:
 Card hw:1 'Generic'/'HD-Audio Generic at 0xd0040000 irq 17'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,00aa0100,00100200'
   Controls : 4
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [off]
Date: Sun Aug 1 21:53:37 2010
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 (20100429.4)
MachineType: ASUSTeK Computer Inc. N61Jq
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-24-generic-pae root=UUID=523dd709-b49a-4834-a2d0-c4a896f52d84 ro quiet splash
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34.1
SourcePackage: linux
dmi.bios.date: 02/04/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N61Jq.206
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N61Jq
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN61Jq.206:bd02/04/2010:svnASUSTeKComputerInc.:pnN61Jq:pvr1.0:rvnASUSTeKComputerInc.:rnN61Jq:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: N61Jq
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

[Alex Nastetsky (seashelf)]

I've found the issue and a workaround, although I think this is still a bug. The issue is that my swap was in a file on my main partition instead of in a separate swap partition. If having a swap file on a non-swap partition works for swap memory in all other respects, seems like it should also work for hibernating. Anyway, I got rid of the swap file and created a proper swap partition and hibernate was able to power down without immediately waking up.

I ran into another issue during the thaw (resume), which is unrelated to the bug, but I thought I would post my solution in case it helps someone. The issue was that it would just hang at a blank screen with a blinking cursor on resuming from hibernate. The solution was to create a /etc/initramfs-tools/conf.d/resume file with RESUME=/dev/sda5 in it, where /dev/sda5 is my swap partition. Then I was able to resume from future hibernations.

[kernel-janitor (kernel-janitor)]

Hi Alex,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. 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. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]