BUG: unable to handle kernel paging request at 00109e25
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
This was collected by apport as I started up an alpha of 9.10. It didn't seem to affect anything els,e but I am reporting it as a good citizen
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 : 'Analog Devices AD1981B'
Components : 'AC97a:41445374'
Controls : 28
Simple ctrls : 20
Date: Mon Sep 21 13:15:03 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=
Lsusb:
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: IBM 2371GHG
Package: linux-image-
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-firmware 1.18
RfKill:
SourcePackage: linux
Tags: kernel-oops
Title: BUG: unable to handle kernel paging request at 00109e25
Uname: Linux 2.6.31-10-generic i686
dmi.bios.date: 06/15/2005
dmi.bios.vendor: IBM
dmi.bios.version: 1UETB6WW (1.66 )
dmi.board.name: 2371GHG
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: 2371GHG
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 430011, 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.