BUG: unable to handle kernel NULL pointer dereference at 0000009c

[Elroy]

Caused by unplugging a usb storage device.

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: Sun Mar 11 09:51:39 2012
Failure: oops
SourcePackage: linux
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: elroy 1571 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Card0.Amixer.info:
 Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with AD1981A at irq 17'
   Mixer name : 'Analog Devices AD1981A'
   Components : 'AC97a:41445372'
   Controls : 25
   Simple ctrls : 17
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=a818f95b-caf9-4a82-bd11-2e3480e5595a
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 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 003 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic root=UUID=481773af-0b0e-47ef-8864-302bf969002c ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-18-generic N/A
 linux-backports-modules-3.2.0-18-generic N/A
 linux-firmware 1.71
RfKill:

Tags: precise
Uname: Linux 3.2.0-18-generic i686
UpgradeStatus: Upgraded to precise on 2012-03-11 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 05/28/2003
dmi.bios.vendor: Compaq
dmi.bios.version: 686O2 v2.21
dmi.board.name: 07E4h
dmi.board.vendor: Compaq
dmi.chassis.type: 15
dmi.chassis.vendor: Compaq
dmi.modalias: dmi:bvnCompaq:bvr686O2v2.21:bd05/28/2003:svnCompaq:pn:pvr:rvnCompaq:rn07E4h:rvr:cvnCompaq:ct15:cvr:
dmi.sys.vendor: Compaq

[Elroy (md7x)]

apport information

[Elroy (md7x)]

apport information

[Elroy (md7x)]

apport information

[Elroy (md7x)]

apport information

[Elroy (md7x)]

apport information

[Elroy (md7x)]

apport information

[Elroy (md7x)]

apport information

[Elroy (md7x)]

apport information

[Elroy (md7x)]

apport information

[Elroy (md7x)]

apport information

[Elroy (md7x)]

apport information

[Elroy (md7x)]

apport information

[Elroy (md7x)]

apport information

[Elroy (md7x)]

apport information

[Elroy (md7x)]

apport information

[Elroy (md7x)]

apport information

[Elroy (md7x)]

apport information

[Elroy (md7x)]

apport information

[Elroy (md7x)]

apport information

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Joseph Salisbury (jsalisbury)]

There is a test kernel available for this bug at:
  http://people.canonical.com/~apw/lp922906-precise/

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