BUG: unable to handle kernel NULL pointer dereference at 00000004

Bug #922460 reported by Patrick Campanale
0
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
High
Unassigned

Bug Description

This is the second time this has happened in the past 10 minutes. filing as security issue now.

ProblemType: KernelOops
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-10-generic 3.2.0-10.18
ProcVersionSignature: Ubuntu 3.2.0-10.18-generic 3.2.1
Uname: Linux 3.2.0-10-generic i686
NonfreeKernelModules: wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
Annotation: Your system might become unstable now and might need to be restarted.
ApportVersion: 1.91-0ubuntu1
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: patrick 1725 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xb4400000 irq 44'
   Mixer name : 'Intel IbexPeak HDMI'
   Components : 'HDA:10ec0272,10250487,00100001 HDA:80862804,80860101,00100000'
   Controls : 23
   Simple ctrls : 12
Date: Fri Jan 27 01:16:55 2012
Failure: oops
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
MachineType: Gateway NV55C
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-10-generic root=UUID=A004D60804D5E178 loop=/hostname/disks/root.disk ro quiet splash vt.handoff=7
PulseSinks: Error: command ['pacmd', 'list-sinks'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
PulseSources: Error: command ['pacmd', 'list-sources'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-1ubuntu18
SourcePackage: linux
StagingDrivers: mei
Title: BUG: unable to handle kernel NULL pointer dereference at 00000004
UpgradeStatus: Upgraded to precise on 2012-01-24 (2 days ago)
dmi.bios.date: 04/25/2011
dmi.bios.vendor: Gateway
dmi.bios.version: V1.21
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: NV55C
dmi.board.vendor: Gateway
dmi.board.version: V1.21
dmi.chassis.type: 10
dmi.chassis.vendor: Gateway
dmi.chassis.version: V1.21
dmi.modalias: dmi:bvnGateway:bvrV1.21:bd04/25/2011:svnGateway:pnNV55C:pvrV1.21:rvnGateway:rnNV55C:rvrV1.21:cvnGateway:ct10:cvrV1.21:
dmi.product.name: NV55C
dmi.product.version: V1.21
dmi.sys.vendor: Gateway

Revision history for this message
Patrick Campanale (patrickappcreator) wrote :
security vulnerability: yes → no
security vulnerability: yes → no
visibility: private → public
visibility: private → public
Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.2.0-14.23)

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.

Changed in linux (Ubuntu):
status: New → Confirmed
status: Confirmed → Incomplete
tags: added: kernel-request-3.2.0-14.23
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
importance: Undecided → High
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

This looks like a duplicate of bug 914319 so I am marking it as such. Please continue to track this issue at that report. Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.