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

[Fabnbox]

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: fabien 1653 F.... pulseaudio
CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfdff8000 irq 16'
   Mixer name : 'Realtek ALC888'
   Components : 'HDA:10ec0888,105be619,00100001'
   Controls : 35
   Simple ctrls : 20
Date: Sun Nov 1 11:58:41 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=UUID=09c4c813-126d-46dc-bbc3-d8e39dab3282
MachineType: Acer Aspire L310
Package: linux-image-2.6.31-14-generic 2.6.31-14.48
ProcCmdLine: root=UUID=122c15b3-57fa-496e-91e2-b48d3e7d929b 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:

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
WpaSupplicantLog:

dmi.bios.date: 01/16/2007
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: R01-A3
dmi.board.name: FI946GZ
dmi.board.vendor: Acer
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrR01-A3:bd01/16/2007:svnAcer:pnAspireL310:pvrR01-A3:rvnAcer:rnFI946GZ:rvr:cvnAcer:ct3:cvr:
dmi.product.name: Aspire L310
dmi.product.version: R01-A3
dmi.sys.vendor: Acer

[Leann Ogasawara (leannogasawara)]

Hi Fabnbox,

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