I'm not sure what happened
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
this crash report was generated just after version upgrade from 9.04 to 9.10
ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'I82801DBICH4'
Mixer name : 'SigmaTel STAC9752,53'
Components : 'AC97a:83847652'
Controls : 38
Simple ctrls : 24
Date: Sat Oct 31 12:19:31 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=
Lsusb:
Bus 001 Device 002: ID 1058:0701 Western Digital Technologies, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Gateway Gateway 450ROG
Package: linux-image-
PccardctlIdent:
Socket 0:
no product info available
Socket 1:
no product info available
PccardctlStatus:
Socket 0:
no card
Socket 1:
no card
ProcCmdLine: root=UUID=
ProcVersionSign
RelatedPackageV
linux-
linux-firmware 1.24
RfKill:
SourcePackage: linux
Tags: kernel-oops
Title: WARNING: at /build/
Uname: Linux 2.6.31-14-generic i686
dmi.bios.date: 04/15/2004
dmi.bios.vendor: Gateway
dmi.bios.version: 40.02.04
dmi.board.name: Gateway 450ROG
dmi.board.vendor: Gateway
dmi.board.version: Rev 1.0
dmi.chassis.
dmi.chassis.type: 8
dmi.chassis.vendor: Gateway
dmi.chassis.
dmi.modalias: dmi:bvnGateway:
dmi.product.name: Gateway 450ROG
dmi.product.
dmi.sys.vendor: Gateway
Hi andy-y,
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 5.008 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.]