BUG: unable to handle kernel NULL pointer dereference at 00000004
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Don't know what happened, after closing virtalbox message appeared.
ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
Card0.Amixer.info:
Card hw:0 'I82801DBICH4'
Mixer name : 'Realtek ALC655 rev 0'
Components : 'AC97a:414c4760'
Controls : 41
Simple ctrls : 26
Date: Wed Nov 4 02:46:31 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Lsusb:
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 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: MTC CANYON-INTEL ODEM
Package: linux-image-
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-firmware 1.24
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Tags: kernel-oops
Title: BUG: unable to handle kernel NULL pointer dereference at 00000004
Uname: Linux 2.6.31-14-generic i686
dmi.bios.date: 09/30/2004
dmi.bios.vendor: Insyde Software Corporation
dmi.bios.version: R1.00
dmi.board.name: CANYON-Intel ODEM
dmi.board.vendor: MTC
dmi.board.version: FAB-3
dmi.chassis.
dmi.chassis.type: 8
dmi.chassis.vendor: MTC
dmi.chassis.
dmi.modalias: dmi:bvnInsydeSo
dmi.product.name: CANYON-INTEL ODEM
dmi.product.
dmi.sys.vendor: MTC
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.