BUG: unable to handle kernel paging request at ffff88024cae633a
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Triaged
|
Undecided
|
Unassigned |
Bug Description
This crashed in AA, it seems.
[87062.867889] Call Trace:
[87062.867894] [<ffffffff8127a
[87062.867898] [<ffffffff8127b
[87062.867903] [<ffffffff8127c
[87062.867909] [<ffffffff81087
[87062.867914] [<ffffffff8124d
[87062.867920] [<ffffffff81146
[87062.867924] [<ffffffff81147
[87062.867929] [<ffffffff812b7
[87062.867934] [<ffffffff81011
[87062.867938] [<ffffffff81013
And it happened when I ran:
$ fakeroot debian/rules build
/usr/bin/fakeroot: line 178: 7280 Killed FAKEROOTKEY=
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: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xe0420000 irq 22'
Mixer name : 'Realtek ALC268'
Components : 'HDA:10ec0268,
Controls : 17
Simple ctrls : 11
Date: Thu Mar 11 15:35:35 2010
DistroRelease: Ubuntu 10.04
Failure: oops
Frequency: This has only happened once.
HibernationDevice: RESUME=/dev/md1
Package: linux-image-
ProcCmdLine: BOOT_IMAGE=
ProcVersionSign
Regression: Yes
RelatedPackageV
Reproducible: No
RfKill:
SourcePackage: linux
TestedUpstream: No
Title: BUG: unable to handle kernel paging request at ffff88024cae633a
Uname: Linux 2.6.32-16-generic x86_64
WpaSupplicantLog:
dmi.bios.date: 09/22/2008
dmi.bios.vendor: Intel Corp.
dmi.bios.version: JOQ3510J.
dmi.board.
dmi.board.name: DQ35JO
dmi.board.vendor: Intel Corporation
dmi.board.version: AAD82085-800
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCor
I cannot reproduce this after a reboot. (My system hung eventually.) It appeared to be sensitive to having a "~" in the path I was running from. Very odd.