A crash report after turning on from hibernation

[dnnowak]

Just a crash report after turning on from hibernation. That's all and everything is still working.

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: damian 1543 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xb0000000 irq 16'
   Mixer name : 'Analog Devices AD1986A'
   Components : 'HDA:11d41986,17c02017,00100500 HDA:10573055,10573055,00100700'
   Controls : 25
   Simple ctrls : 16
Date: Fri Nov 20 17:36:44 2009
DistroRelease: Ubuntu 9.10
Failure: oops
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MachineType: FUJITSU SIEMENS AMILO Pro V2085
Package: linux-image-2.6.31-14-generic 2.6.31-14.48
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=/dev/sda2 loop=/hostname/disks/root.disk 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:
 1: phy3: 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: 02/18/2006
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: R01-A1I
dmi.board.name: AMILO Pro V2085
dmi.board.vendor: FUJITSU SIEMENS
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.chassis.version: A2040
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR01-A1I:bd02/18/2006:svnFUJITSUSIEMENS:pnAMILOProV2085:pvr20:rvnFUJITSUSIEMENS:rnAMILOProV2085:rvr:cvnFUJITSUSIEMENS:ct10:cvrA2040:
dmi.product.name: AMILO Pro V2085
dmi.product.version: 20
dmi.sys.vendor: FUJITSU SIEMENS

[Leann Ogasawara (leannogasawara)]

Hi dnnowak,

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