BUG: unable to handle kernel NULL pointer dereference at 00000004
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Invalid
|
Medium
|
Unassigned |
Bug Description
No idea what caused it to crash, i'm just happy the kernel is finally reporting crashes :D
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 'SB'/'HDA ATI SB at 0xfe020000 irq 16'
Mixer name : 'Realtek ALC883'
Components : 'HDA:10ec0883,
Controls : 39
Simple ctrls : 22
Card1.Amixer.info:
Card hw:1 'Webcam'
Mixer name : 'USB Mixer'
Components : 'USB05a9:2649'
Controls : 4
Simple ctrls : 3
Date: Wed Sep 9 15:02:50 2009
DistroRelease: Ubuntu 9.10
Failure: oops
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
pan0 no wireless extensions.
MachineType: System manufacturer System Product Name
Package: linux-image-
PccardctlIdent:
PccardctlStatus:
ProcCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
RfKill:
0: hci0: Bluetooth
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-10-generic i686
dmi.bios.date: 02/05/2009
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS M2A-VM ACPI BIOS Revision 2302
dmi.board.name: M2A-VM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: System Product Name
dmi.product.
dmi.sys.vendor: System manufacturer
tags: | added: regression-potential |
Changed in linux (Ubuntu): | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in linux (Ubuntu): | |
status: | Won't Fix → New |
tags: |
added: regression-release removed: regression-potential |
tags: | added: karmic |
Changed in linux (Ubuntu): | |
assignee: | Andy Whitcroft (apw) → nobody |
Changed in linux (Ubuntu): | |
status: | Incomplete → Invalid |
That Ooops stack says something so bad occured that neither the EIP nor SP for the process were valid. This leaves us with almost no information. Is this reproducible at all on the latest Karmic kernel? If not we really are not likely to be able to figure out what the trigger was from what was collected. From what we have we cannot fix this, so I'll mark it Won't Fix, but if you are able to reproduce it please do reopen this bug.