BUG: unable to handle kernel NULL pointer dereference at 0000000000000010

Bug #1229118 reported by Nicola
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

During normal use, the system crashed reporting this message:
BUG: unable to handle kernel NULL pointer dereference at 0000000000000010
I am attaching the kernel backtrace that was dumped to the console and to kern.log

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-54-generic 3.2.0-54.82
ProcVersionSignature: Ubuntu 3.2.0-54.82-generic 3.2.50
Uname: Linux 3.2.0-54-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: nicola 2291 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xe2e60000 irq 47'
   Mixer name : 'Intel CougarPoint HDMI'
   Components : 'HDA:111d76e7,10280492,00100102 HDA:80862805,80860101,00100000'
   Controls : 37
   Simple ctrls : 13
Date: Mon Sep 23 12:06:37 2013
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
MachineType: Dell Inc. Latitude E6320
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-54-generic root=UUID=1efb2c8a-140f-4f44-9a98-fe9c6810c31c ro crashkernel=384M-2G:64M,2G-:128M quiet splash drm_kms_helper.poll=0 vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-54-generic N/A
 linux-backports-modules-3.2.0-54-generic N/A
 linux-firmware 1.79.6
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: Upgraded to precise on 2012-08-27 (392 days ago)
dmi.bios.date: 03/07/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 0GJF11
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA17:bd03/07/2013:svnDellInc.:pnLatitudeE6320:pvr01:rvnDellInc.:rn0GJF11:rvrA01:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6320
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

Revision history for this message
Nicola (nicobaldo) wrote :
Revision history for this message
Nicola (nicobaldo) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of the introduction of a regression, and when this regression was introduced. If this is a regression, we can perform a kernel bisect to identify the commit that introduced the problem.

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.12 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc1-saucy/

Revision history for this message
Nicola (nicobaldo) wrote :

Hi Josep,

yes this bug appeared after an upgrade, I was previously using kernel 3.2.0-47 and this bug did not occur.
I am attaching another trace that I got again with kernel 3.2.0-54, the overall symptom is the same (system crashes) though the kernel log looks a bit different.

I'll give a try to the mainline kernel and let you know.

Revision history for this message
Nicola (nicobaldo) wrote :

I've been running 3.12.0-031200rc1-generic for about a month and the bug never occurred

tags: added: kernel-fixed-upstream
Revision history for this message
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  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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