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) |
Expired
|
Medium
|
Unassigned |
Bug Description
Happend after waking up from suspend.
The only obvious setback is that 3D apps stutter (low fps).
My guess is:
It is related to the multi-core cpu or the switching of cpu cores.
If I restrict the 3D apps to using only one cpu core the problem is gone.
ProblemType: KernelOops
DistroRelease: Ubuntu 10.04
Package: linux-image-
Regression: Yes
Reproducible: No
ProcVersionSign
Uname: Linux 2.6.32-19-generic x86_64
NonfreeKernelMo
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 'Audigy'/'SB Audigy 1 [SB0090] (rev.3, serial:0x511102) at 0xec00, irq 22'
Mixer name : 'TriTech TR28602'
Components : 'AC97a:54524123'
Controls : 194
Simple ctrls : 30
Date: Mon Apr 5 10:16:17 2010
Failure: oops
Frequency: This has only happened once.
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100312)
MachineType: System manufacturer System Product Name
ProcCmdLine: BOOT_IMAGE=
RelatedPackageV
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: WARNING: at /build/
dmi.bios.date: 03/04/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0604
dmi.board.
dmi.board.name: M4A785TD-V EVO
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
tags: | removed: regression-potential |
Hi Laryllan,
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.170 seconds. I'm setting this to traiged for further investigation. Thanks!
[This is an automated message. Apologies if it has reached you inappropriately.]