Ubuntu
linux package

BUG: unable to handle kernel NULL pointer dereference at 0000000000000028

Bug #534609 reported by ingo on 2010-03-08

This bug report is a duplicate of: Bug #535297: BUG: unable to handle kernel NULL pointer dereference at 0000000000000028. Edit Remove

This bug affects 5 people

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Happened in Lucid-amd64 after today's kernel-update -> 2.6.32-16

Happens regularly after booting when x-server starts. Only low-graphics-mode posssible.

All was fine until today with kernel 2.6.32-15

ProblemType: KernelOops
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Annotation: Your system might become unstable now and might need to be restarted.
AplayDevices:
**** List of PLAYBACK Hardware Devices ****
card 0: I82801AAICH [Intel 82801AA-ICH], device 0: Intel ICH [Intel 82801AA-ICH]
   Subdevices: 0/1
   Subdevice #0: subdevice #0
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: ingo 1353 F.... pulseaudio
/dev/snd/pcmC0D0p: ingo 1353 F...m pulseaudio
/dev/snd/timer: ingo 1353 f.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'I82801AAICH'/'Intel 82801AA-ICH with STAC9700,83,84 at irq 21'
   Mixer name : 'SigmaTel STAC9700,83,84'
   Components : 'AC97a:83847600'
   Controls : 34
   Simple ctrls : 24
Date: Mon Mar 8 20:33:09 2010
DistroRelease: Ubuntu 10.04
Failure: oops
HibernationDevice: RESUME=UUID=24794838-62d2-44f9-bdca-99830c43bf10
IwConfig:
lo no wireless extensions.

eth0 no wireless extensions.
Lsusb:
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: innotek GmbH VirtualBox
Package: linux-image-2.6.32-16-generic 2.6.32-16.24
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-16-generic root=UUID=6d3e024e-843b-4e74-a5e7-f21925d39aef ro quiet splash
ProcVersionSignature: Ubuntu 2.6.32-16.24-generic
Regression: Yes
RelatedPackageVersions: linux-firmware 1.32
Reproducible: Yes
RfKill:

SourcePackage: linux
TestedUpstream: No
Title: BUG: unable to handle kernel NULL pointer dereference at 0000000000000028
Uname: Linux 2.6.32-16-generic x86_64
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

Tags:

Revision history for this message

ingo (ingo-steiner) wrote on 2010-03-08:

AlsaDevices.txt Edit (405 bytes, text/plain; charset="utf-8")
ArecordDevices.txt Edit (318 bytes, text/plain; charset="utf-8")
BootDmesg.txt Edit (23.1 KiB, text/plain; charset="utf-8")
Card0.Amixer.values.txt Edit (5.3 KiB, text/plain; charset="utf-8")
Card0.Codecs.codec97.0.ac97.0.0.txt Edit (687 bytes, text/plain; charset="utf-8")
Card0.Codecs.codec97.0.ac97.0.0.regs.txt Edit (767 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (22.6 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (5.0 KiB, text/plain; charset="utf-8")
OopsText.txt Edit (2.6 KiB, text/plain; charset="utf-8")
PciMultimedia.txt Edit (559 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.3 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.3 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.0 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (63.4 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (136.2 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (348.1 KiB, text/plain; charset="utf-8")

Revision history for this message

Ryan Steele (rgsteele) wrote on 2010-03-08:

Confirmed. Like the reporter I am also running 64-bit in a Virtualbox VM with the "low-graphics mode" issue, although this bug appears to be ALSA-related.

Changed in linux (Ubuntu):
status:	New → Confirmed

Revision history for this message

Ryan Steele (rgsteele) wrote on 2010-03-11:

The issue with Xorg failing to start appears to be an incompatibility between the VirtualBox Guest Additions and the new version of the kernel. There is a workaround in the bug report here:

http://www.virtualbox.org/ticket/6198