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) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
After waking up from suspend, this occured.
But the system is running fine, the wake up was quick and sound is working.
ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/pcmC0D0p: dominik 3117 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'SB'/'HDA ATI SB at 0xfe020000 irq 16'
Mixer name : 'Realtek ALC883'
Components : 'HDA:10ec0883,
Controls : 38
Simple ctrls : 21
Card1.Amixer.info:
Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfdbfc000 irq 19'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,
Controls : 4
Simple ctrls : 1
Card1.Amixer.
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined
Playback channels: Mono
Mono: Playback [off]
Date: Fri Oct 23 18:54:58 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
vboxnet0 no wireless extensions.
MachineType: System manufacturer System Product Name
NonfreeKernelMo
Package: linux-image-
ProcCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-firmware 1.24
RfKill:
SourcePackage: linux
Tags: kernel-oops
Title: WARNING: at /build/
Uname: Linux 2.6.31-14-generic x86_64
WpaSupplicantLog:
dmi.bios.date: 02/05/2009
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS M2A-VM ACPI BIOS Revision 2302
dmi.board.name: M2A-VM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: System Product Name
dmi.product.
dmi.sys.vendor: System manufacturer
Hi Dominik,
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 11.610 seconds. I'm setting this to traiged for further investigation. Thanks!
[This is an automated message. Apologies if it has reached you inappropriately.]