WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:53 suspend_test_finish 0x84/0x90()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I have no idea what's going on.As soon as I turn on the computer and logged in,this error message appeared.
Sorry,I'm not capable of development or finding out the reason of the problem.
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/seq: timidity 2100 F.... timidity
CRDA: Error: [Errno 2] 沒有此一檔案或目錄
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xe1280000 irq 16'
Mixer name : 'Realtek ALC883'
Components : 'HDA:10ec0883,
Controls : 40
Simple ctrls : 22
Date: Fri Apr 23 21:38:12 2010
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=
MachineType: Gigabyte Technology Co., Ltd. G31M-ES2L
Package: linux-image-
ProcCmdLine: root=UUID=
ProcVersionSign
RelatedPackageV
linux-
linux-firmware 1.24
RfKill:
SourcePackage: linux
Tags: kernel-oops
Title: WARNING: at /build/
Uname: Linux 2.6.31-20-generic i686
WpaSupplicantLog:
dmi.bios.date: 02/05/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F8
dmi.board.name: G31M-S2L
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSof
dmi.product.name: G31M-ES2L
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
tags: | added: kernel-suspend |
tags: | added: kj-triage |
tags: | added: karmic |
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. Typically you'll see something similar to "PM: resume devices took 10.408 seconds" in your dmesg output when this happens. 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!