BUG: unable to handle kernel NULL pointer dereference at 00000108
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Incomplete
|
Medium
|
Unassigned |
Bug Description
unstable kernel
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.
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
Card0.Amixer.info:
Card hw:0 'I82801DBICH4'
Mixer name : 'Realtek ALC203 rev 0'
Components : 'AC97a:414c4770'
Controls : 31
Simple ctrls : 20
Date: Tue Mar 9 18:24:00 2010
DistroRelease: Ubuntu 10.04
Failure: oops
Frequency: This has only happened once.
HibernationDevice: RESUME=
Lsusb:
Bus 004 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 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: FUJITSU SIEMENS LIFEBOOK E8010 INT
Package: linux-image-
ProcCmdLine: root=UUID=
ProcVersionSign
Regression: Yes
RelatedPackageV
Reproducible: No
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
TestedUpstream: No
Title: BUG: unable to handle kernel NULL pointer dereference at 00000108
Uname: Linux 2.6.32-16-generic i686
WpaSupplicantLog:
dmi.bios.date: 09/21/2004
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.09
dmi.board.name: FJNB185
dmi.board.vendor: FUJITSU
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.chassis.
dmi.modalias: dmi:bvnFUJITSU/
dmi.product.name: LIFEBOOK E8010 INT
dmi.sys.vendor: FUJITSU SIEMENS
Changed in linux (Ubuntu): | |
status: | Triaged → Incomplete |
tags: | added: i915 |
tags: | added: kernel-driver-i915 |
@ruud:
This bug is caused by the graphics driver. How reproducible is this bug? I suggest openning a bug upstream at bugs.freedeskto p.org. When you do so, please report back with the bug url here so we can link the two bugs.
Thanks