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

[Martin Konecny]

Booted system and as son as I logged in I had this crash report.

ProblemType: KernelOops
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory
Annotation: Your system might become unstable now and might need to be restarted.
AplayDevices: aplay: device_list:223: no soundcards found...
Architecture: i386
ArecordDevices: arecord: device_list:223: no soundcards found...
Date: Thu Nov 12 16:17:59 2009
DistroRelease: Ubuntu 9.10
Failure: oops
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 002: ID 1241:1177 Belkin F8E842-DL Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: ASUS A7V400-MX
Package: linux-image-2.6.31-14-generic 2.6.31-14.48
PciMultimedia:

ProcCmdLine: root=UUID=9807e77b-4d84-4557-b3fe-2250c4c97617 ro quiet splash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: linux
Tags: kernel-oops
Title: [783739.908426] ------------[ cut here ]------------
Uname: Linux 2.6.31-14-generic i686
dmi.bios.date: 12/21/2004
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS A7V400-MX ACPI BIOS Revision 1009
dmi.board.name: A7V400-MX
dmi.board.vendor: ASUSTek Computer INC.
dmi.board.version: 1.03
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: ASUS
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSA7V400-MXACPIBIOSRevision1009:bd12/21/2004:svnASUS:pnA7V400-MX:pvr1.03:rvnASUSTekComputerINC.:rnA7V400-MX:rvr1.03:cvnASUS:ct3:cvrChassisVersion:
dmi.product.name: A7V400-MX
dmi.product.version: 1.03
dmi.sys.vendor: ASUS

[Leann Ogasawara (leannogasawara)]

Hi Martin,

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