WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52 suspend_test_finish+0x80/0x90()

[Felix Oghină]

Suspending acts weird. It takes a long time to actually enter standby and, when coming back from suspend, I get kernel error (in Gnome, I don't see anything in the terminal that flashes before the GUI appears).

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: NVidia [HDA NVidia], device 0: CONEXANT Analog [CONEXANT Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: andrei 1695 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'NVidia'/'HDA NVidia at 0xc0000000 irq 19'
   Mixer name : 'Nvidia MCP78 HDMI'
   Components : 'HDA:14f15051,103c360a,00100000 HDA:10de0002,10de0101,00100000'
   Controls : 18
   Simple ctrls : 8
Date: Sun Nov 1 01:38:05 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=UUID=f5940b59-8864-4bbd-82ae-f612834c6dff
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MachineType: Hewlett-Packard Compaq Presario CQ60 Notebook PC
NonfreeKernelModules: nvidia
Package: linux-image-2.6.31-14-generic 2.6.31-14.48
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=18196c30-468d-45c4-89e5-f4ce80558598 ro quiet splash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-14-generic N/A
 linux-firmware 1.24
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Tags: kernel-oops
Title: WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52 suspend_test_finish+0x80/0x90()
Uname: Linux 2.6.31-14-generic i686
dmi.bios.date: 03/13/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.36
dmi.board.name: 303C
dmi.board.vendor: Wistron
dmi.board.version: 08.51
dmi.chassis.type: 10
dmi.chassis.vendor: Wistron
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.36:bd03/13/2009:svnHewlett-Packard:pnCompaqPresarioCQ60NotebookPC:pvrF.36:rvnWistron:rn303C:rvr08.51:cvnWistron:ct10:cvrN/A:
dmi.product.name: Compaq Presario CQ60 Notebook PC
dmi.product.version: F.36
dmi.sys.vendor: Hewlett-Packard

[Leann Ogasawara (leannogasawara)]

Hi Felix,

The warning reported here typically indicates that it took longer for your system to resume from suspend than expected. I believe there is a 5 sec barrier which your system likely exceeded. Based on your dmesg output I see PM: resume devices took 6.524 seconds. A patch to prevent this warning has been applied via bug 464552. As a result I'm marking this as a duplicate to bug 464552. Please continue to track this issue at that report. Thanks!

[This is an automated message. Apologies if it has reached you inappropriately.]

[Felix Oghină (felix.oghina)]

I will unmark this as a duplicate of bug 464552, here are the differences between my problem and the problem reported there:

1) Coming out of suspend works just fine (and pretty fast). It's going into suspend that takes an unusual long time: Ubuntu goes to a blank screen but then an empty console appears (cursor blinking) and stays there for ~20-30 seconds before it goes to suspend. As a comparison, Windows 7 goes to suspend (well, "sleep") in at most half the time it takes Ubuntu to do so on the same machine.
2) When coming out of suspend, the screen is dimmed, even if the laptop was plugged the whole time, which would indicate some sort of actual error, not just a false timeout.

If there's any other info I could provide I'd be more than happy to.

[yossisynett (yossisynett)]

I've marked this as a duplicate of bug 451282 since they appear to be the same issue. I notice that all the graphics cards concerned are Nvidia.

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Felix Oghină, thank you for reporting this and helping make Ubuntu better. Karmic reached EOL on April 30, 2011.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, could you please provide the full computer model (ex. Compaq Presario CQ60-407AU Notebook PC)?

As well, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory daily folder. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.10-rc2

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Helpful bug reporting tips:
https://help.ubuntu.com/community/ReportingBugs

[Launchpad Janitor (janitor)]

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