WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52 suspend_test_finish+0x80/0x90()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
i am using beta karmic kola.
this bug showed up after doing update 10-9-2009 5:25 pm mtn time.
prior successful update was 10-9-2009 around 10 am.
ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'SI7012'/'SiS SI7012 with AD1980 at irq 18'
Mixer name : 'Analog Devices AD1980'
Components : 'AC97a:41445370'
Controls : 46
Simple ctrls : 32
Card1.Amixer.info:
Card hw:1 'Live'/'SB Live! [Unknown] (rev.10, serial:0x80671102) at 0x8400, irq 18'
Mixer name : 'eMicro EM28028'
Components : 'AC97a:454d4328'
Controls : 216
Simple ctrls : 38
Date: Fri Oct 9 17:14:14 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: System Manufacturer System Name
Package: linux-image-
ProcCmdLine: root=UUID=
ProcVersionSign
RelatedPackageV
RfKill:
SourcePackage: linux
Tags: kernel-oops
Title: WARNING: at /build/
Uname: Linux 2.6.31-13-generic i686
WpaSupplicantLog:
dmi.bios.date: 06/11/2003
dmi.bios.vendor: Award Software, Inc.
dmi.bios.version: ASUS P4S533-MX ACPI BIOS Revision 1006
dmi.board.name: P4S533MX
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: REV 1.xx
dmi.chassis.
dmi.chassis.type: 7
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAwardSof
dmi.product.name: System Name
dmi.product.
dmi.sys.vendor: System Manufacturer
Hi bill,
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 64.420 seconds. I'm setting this to traiged for further investigation. Thanks!
[This is an automated message. Apologies if it has reached you inappropriately.]