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

[Louis Bodnar]

I don't know what crashed. Ubuntu just said that something bad happened and that I should submit a bug report. I hope the report contains useful information because I didn't even know something crashed.

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: louis 1804 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf8400000 irq 20'
   Mixer name : 'Realtek ALC268'
   Components : 'HDA:10ec0268,14c00023,00100003 HDA:10573055,10573055,00100700'
   Controls : 19
   Simple ctrls : 13
Date: Fri Oct 30 23:09:07 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=UUID=be8a3126-48f9-4951-b7c6-a24a4b5ec852
InstallationMedia: Ubuntu-Netbook-Remix 9.10 "Karmic Koala" - Release i386 (20091028.4)
MachineType: - N/A
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=79e594e7-f13d-40a3-bd9a-b1834a3dafba 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
SourcePackage: linux
Tags: kernel-oops ubuntu-unr
Title: 3] ------------[ cut here ]------------
Uname: Linux 2.6.31-14-generic i686
dmi.bios.date: 08/29/2007
dmi.bios.vendor: COMPAL
dmi.bios.version: 1.12
dmi.board.name: IFT00
dmi.board.vendor: -
dmi.board.version: IFT00
dmi.chassis.asset.tag: -
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnCOMPAL:bvr1.12:bd08/29/2007:svn-:pnN/A:pvrN/A:rvn-:rnIFT00:rvrIFT00:cvnNoEnclosure:ct10:cvrN/A:
dmi.product.name: N/A
dmi.product.version: N/A
dmi.sys.vendor: -

[Leann Ogasawara (leannogasawara)]

Hi pez,

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.520 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.]