WARNING: at /build/buildd/linux-2.6.32/kernel/power/suspend_test.c:53 suspend_test_finish+0x88/0x90()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
just posting screenlet bug and this issue occur
ProblemType: KernelOops
DistroRelease: Ubuntu 10.04
Package: linux-image-
Regression: No
Reproducible: No
ProcVersionSign
Uname: Linux 2.6.32-20-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: amd64
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 0xfe7f8000 irq 22'
Mixer name : 'Realtek ALC1200'
Components : 'HDA:10ec0888,
Controls : 40
Simple ctrls : 22
Card1.Amixer.info:
Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfe8fc000 irq 17'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,
Controls : 4
Simple ctrls : 1
Card1.Amixer.
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Date: Tue Apr 13 09:25:13 2010
Failure: oops
Frequency: This has only happened once.
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100321)
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
MachineType: System manufacturer System Product Name
ProcCmdLine: BOOT_IMAGE=
RelatedPackageV
RfKill:
SourcePackage: linux
Title: WARNING: at /build/
dmi.bios.date: 10/02/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1406
dmi.board.
dmi.board.name: P5Q
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: System Product Name
dmi.product.
dmi.sys.vendor: System manufacturer
Hi .salo,
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 8.664 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!
[This is an automated message. Apologies if it has reached you inappropriately.]