The system came out of standby on its own
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Mobo: Asus M2N32-SLI Deluxe Wireless Edition
Graphics card: GIGABYTE GV-NX86T256D GeForce 8600 GT
CPU: Phenom 9500
Memory: 8GGB
The system has also freezes after a while of playing music on Rythmbox. This happened at the beging of the relese of 9.04 but was fixed later, now it seems to be back? I'll be happy to provide any system info. requested.
ProblemType: KernelOops
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 'Audigy2'/'SB Audigy 2 ZS [SB0350] (rev.4, serial:0x20021102) at 0xcc00, irq 18'
Mixer name : 'SigmaTel STAC9721,23'
Components : 'AC97a:83847609'
Controls : 210
Simple ctrls : 46
Date: Sat Oct 31 00:00:10 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: System manufacturer System Product Name
NonfreeKernelMo
Package: linux-image-
ProcCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-firmware 1.24
RfKill:
1: phy1: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Tags: kernel-oops
Title: WARNING: at /build/
Uname: Linux 2.6.31-14-generic x86_64
WifiSyslog:
dmi.bios.date: 03/02/2009
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS M2N32-SLI DELUXE ACPI BIOS Revision 2205
dmi.board.name: M2N32-SLI DELUXE
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
affects: | ubuntu → linux (Ubuntu) |
Hi Heber,
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 6.840 seconds. 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.]