BUG: unable to handle kernel NULL pointer dereference at 0000000000000008
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
on Ubuntu 10.10 startup apport reported Kernel Bug
ProblemType: KernelOops
DistroRelease: Ubuntu 10.10
Package: linux-image-
Regression: Yes
Reproducible: No
ProcVersionSign
Uname: Linux 2.6.35-19-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'SB'/'HDA ATI SB at 0xfe024000 irq 16'
Mixer name : 'Realtek ALC889A'
Components : 'HDA:10ec0885,
Controls : 38
Simple ctrls : 21
Card1.Amixer.info:
Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfdefc000 irq 45'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,
Controls : 4
Simple ctrls : 1
Card1.Amixer.
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [off]
Date: Wed Sep 1 16:42:22 2010
Failure: oops
Frequency: This has only happened once.
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100803.1)
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
ppp0 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. GA-MA790X-UD4P
ProcCmdLine: BOOT_IMAGE=
RelatedPackageV
RfKill:
SourcePackage: linux
Title: BUG: unable to handle kernel NULL pointer dereference at 0000000000000008
dmi.bios.date: 08/12/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F7
dmi.board.name: GA-MA790X-UD4P
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSof
dmi.product.name: GA-MA790X-UD4P
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
Hi,
We believe that this bug was fixed by a new kernel (2.6.35-21.30) released a couple of weeks ago. Please test that the
sudo lshw
command completes on your machine without an oops, and comment here either way.
Dave