WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52 suspend_test_finish+0x7c/0x80()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
When bringing my laptop back from suspend (opening the lid) the computer boots, goes to ubuntu (though nothing is shown on the screen, but there is harddisk activity), then, right when the login box that usually comes up after un-suspending should pop up, it goes back in suspend (doesen't shut down, just suspends, instantly).
When I then press the power button to bring it out of suspend mode, it works, login box pops up, and it allows me acces to the system.
ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: amd64
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/seq: timidity 3043 F.... timidity
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xefffc000 irq 21'
Mixer name : 'SigmaTel STAC9200'
Components : 'HDA:83847690,
Controls : 12
Simple ctrls : 7
Date: Fri Oct 30 18:32:47 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=
MachineType: Dell Inc. Latitude D820
NonfreeKernelMo
Package: linux-image-
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: root=UUID=
ProcVersionSign
RelatedPackageV
linux-
linux-firmware 1.24
SourcePackage: linux
Tags: kernel-oops
Title: WARNING: at /build/
Uname: Linux 2.6.31-14-generic x86_64
WpaSupplicantLog:
dmi.bios.date: 06/15/2007
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 0JF242
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Latitude D820
dmi.sys.vendor: Dell Inc.
Hi Andrei,
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.860 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.]