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
i saw that message when i opened my laptop screen after close it.
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: 2/2
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] No existe el fichero ó directorio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfb300000 irq 22'
Mixer name : 'SigmaTel STAC9205'
Components : 'HDA:838476a0,
Controls : 23
Simple ctrls : 14
Date: Sat May 8 12:29:50 2010
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: Arima W651DI
Package: linux-image-
ProcCmdLine: BOOT_IMAGE=
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
dmi.bios.date: 11/12/2007
dmi.bios.vendor: Arima
dmi.bios.version: 92.0B
dmi.board.vendor: Arima
dmi.board.version: Rev1.92.0B
dmi.chassis.
dmi.chassis.type: 8
dmi.chassis.vendor: Arima
dmi.chassis.
dmi.modalias: dmi:bvnArima:
dmi.product.name: W651DI
dmi.product.
dmi.sys.vendor: Arima
tags: | added: kernel-suspend |
tags: | added: kj-triage |
Hi,
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 13.440 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!