Kernel Oops - BUG: unable to handle kernel NULL pointer dereference at 0000009c; EIP is at __ticket_spin_lock+0x8/0x30
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
.
ProblemType: KernelOops
DistroRelease: Ubuntu 12.04
Package: linux-image-
ProcVersionSign
Uname: Linux 3.2.0-22-generic i686
NonfreeKernelMo
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
Annotation: Your system might become unstable now and might need to be restarted.
ApportVersion: 2.0-0ubuntu4
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
Date: Fri Apr 6 14:27:42 2012
Failure: oops
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
MachineType: Hewlett-Packard HP Mini
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageV
SourcePackage: linux
Title: BUG: unable to handle kernel NULL pointer dereference at 0000009c
UpgradeStatus: Upgraded to precise on 2012-03-04 (33 days ago)
dmi.bios.date: 04/30/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 361A0 Ver. F.16
dmi.board.name: 361A
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 02.12
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP Mini
dmi.product.
dmi.sys.vendor: Hewlett-Packard
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
Changed in linux (Ubuntu): | |
importance: | Undecided → Medium |
status: | Incomplete → Confirmed |
tony b, thank you for reporting this bug and helping make Ubuntu better. Please answer these questions:
* Is this reproducible? /wiki.ubuntu. com/KernelMainl ineBuilds . Once you've tested the upstream kernel, please remove the 'needs- upstream- testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs- upstream- testing' text. Please let us know your results.
* If so, what specific steps should we take to recreate this bug?
* Could you please test the latest upstream kernel available? It will allow additional upstream developers to examine the issue. Refer to https:/
Thanks in advance.