Kernel Error After Resume
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Not sure what exactly this bug is, got a message saying their was a kernel error, the system might be unstable and should be rebooted. Also my GPU fan is not returning to idle but I think that is a problem with the Radeon package and not this one.
ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'XFi'/'Creative X-Fi 20K1 Unknown'
Mixer name : '20K1'
Components : ''
Controls : 30
Simple ctrls : 11
Card1.Amixer.info:
Card hw:1 'Intel'/'HDA Intel at 0xf0100000 irq 22'
Mixer name : 'Realtek ALC888'
Components : 'HDA:10ec0888,
Controls : 40
Simple ctrls : 22
Date: Mon Nov 2 09:40:56 2009
DistroRelease: Ubuntu 9.10
Failure: oops
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
vboxnet0 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. 965P-DQ6
Package: linux-image-
ProcCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-firmware 1.24
RfKill:
SourcePackage: linux
Tags: kernel-oops
Title: [149719.290040] ------------[ cut here ]------------
Uname: Linux 2.6.31-14-generic x86_64
dmi.bios.date: 06/25/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F13
dmi.board.name: 965P-DQ6
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSof
dmi.product.name: 965P-DQ6
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
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.