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) |
New
|
Undecided
|
Unassigned |
Bug Description
bla
ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
AplayDevices:
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0x58340000 irq 16'
Mixer name : 'Realtek ALC272'
Components : 'HDA:10ec0272,
Controls : 14
Simple ctrls : 9
Date: Fri Nov 6 19:47:21 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=
MachineType: Acer Aspire one
NonfreeKernelMo
Package: linux-image-
ProcCmdLine: root=UUID=
ProcVersionSign
RelatedPackageV
linux-
linux-firmware 1.24
RfKill:
SourcePackage: linux
Tags: kernel-oops ubuntu-unr
Title: WARNING: at /build/
Uname: Linux 2.6.31-14-generic i686
WpaSupplicantLog:
dmi.bios.date: 07/09/2009
dmi.bios.vendor: Acer
dmi.bios.version: V1.08
dmi.board.
dmi.board.name: Aspire one
dmi.board.vendor: Acer
dmi.board.version: V1.08
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.
dmi.modalias: dmi:bvnAcer:
dmi.product.name: Aspire one
dmi.product.
dmi.sys.vendor: Acer
Hi DANrulz81,
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 3.304 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.]