Kernel Oops - BUG: unable to handle kernel NULL pointer dereference at (null); EIP is at __ticket_spin_lock+0x8/0x30

Bug #977071 reported by Shock on 2012-04-09
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)

Bug Description

This happens every time I try to pair a bluetooth mouse. This used to work in 11.04 but I still get the oops in 11.10. Please fix this as it means that I'm stuck with 11.04.

ProblemType: KernelOops
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-18-generic
Uname: Linux 3.2.0-18-generic i686
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
Date: Thu Mar 15 20:13:56 2012
Failure: oops
SourcePackage: linux

Shock (mmiron) wrote :

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 977071

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: precise
summary: - BUG: unable to handle kernel NULL pointer dereference at (null)
+ Kernel Oops - BUG: unable to handle kernel NULL pointer dereference at
+ (null); EIP is at __ticket_spin_lock+0x8/0x30
Shock (mmiron) wrote :

apport-collect spew some tracebacks on the terminal and hang indefinitely, so I can't add more info.

Joseph Salisbury (jsalisbury) wrote :

There is a test kernel available for this bug at:

Can you test this kernel and report back in bug 922906 where or not the test kernel resolved this bug?

Shock (mmiron) wrote :

I'm still getting the kernel oops with the apw kernel from bug #922906. I'm removing the duplicate status since it does not seem to be a duplicate. All the patches I've seen in the apw kernel have to do with inotify/fsnotify. I'm triggering the bug by connecting a bluetooth mouse. The problem seems to be at a lower level in the kernel since the same panic is triggered by two different things (usb-unplug and bluetooth pairing).

Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments