WARNING: at /build/buildd/linux-2.6.38/kernel/power/suspend_test.c:53 suspend_test_finish+0x89/0x90()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Medium
|
Unassigned |
Bug Description
suspend, then when I turn it on, the error message came up
ProblemType: KernelOops
DistroRelease: Ubuntu 11.04
Package: linux-image-
Regression: Yes
Reproducible: Yes
ProcVersionSign
Uname: Linux 2.6.38-
NonfreeKernelMo
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/pcmC0D0p: bigmouse 1568 F...m pulseaudio
CRDA: Error: [Errno 2] 没有那个文件或目录
Card0.Amixer.info:
Card hw:0 'SB'/'HDA ATI SB at 0xf9ff4000 irq 16'
Mixer name : 'Realtek ALC887'
Components : 'HDA:10ec0887,
Controls : 33
Simple ctrls : 19
Card1.Amixer.info:
Card hw:1 'NVidia'/'HDA NVidia at 0xfbc7c000 irq 19'
Mixer name : 'Nvidia GPU 0d HDMI/DP'
Components : 'HDA:10de000d,
Controls : 16
Simple ctrls : 4
Date: Tue Apr 12 12:24:10 2011
Failure: oops
HibernationDevice: RESUME=/dev/sdc1
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
linux-
linux-
linux-firmware 1.50
RfKill:
SourcePackage: linux
Title: WARNING: at /build/
UpgradeStatus: Upgraded to natty on 2011-04-05 (6 days ago)
dmi.bios.date: 05/05/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0309
dmi.board.
dmi.board.name: M4A78-EM-1394
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
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 Michael,
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 10.236 seconds. I'm setting this to traiged for further investigation. Thanks!
[This is an automated message. Apologies if it has reached you inappropriately.]