[117348.028327] ------------[ cut here ]------------
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
A kernel bug on wakeup.
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 'ICH6'/'Intel ICH6 with AD1981B at irq 22'
Mixer name : 'Analog Devices AD1981B'
Components : 'AC97a:41445374'
Controls : 26
Simple ctrls : 18
Date: Thu Oct 8 12:57:48 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=
Lsusb:
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
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: IBM 1858A32
Package: linux-image-
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: root=UUID=
ProcVersionSign
RelatedPackageV
linux-
linux-firmware 1.20
RfKill:
SourcePackage: linux
Tags: kernel-oops
Title: [117348.028327] ------------[ cut here ]------------
Uname: Linux 2.6.31-11-generic i686
WpaSupplicantLog:
dmi.bios.date: 07/15/2005
dmi.bios.vendor: IBM
dmi.bios.version: 70ET57WW (1.17 )
dmi.board.name: 1858A32
dmi.board.vendor: IBM
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: IBM
dmi.chassis.
dmi.modalias: dmi:bvnIBM:
dmi.product.name: 1858A32
dmi.product.
dmi.sys.vendor: IBM
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 417842, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.