Kernel crash when clicking on crash reporter (!) - BUG: unable to handle kernel paging request at 0019a8c4

Bug #440530 reported by Andrew Brown on 2009-10-02
104
This bug affects 25 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Undecided
Unassigned

Bug Description

I had a separate kernel crash when suspending (which has been reported). However, when the machine restarted, the crash reporter icon was present in the notification tray, and after working for some hours I clicked it, just to be tidy. Immediately. I got a second crash, which I am now reporting. This has happened before, but I did not identify it because it looked as if the same crash were being reported twice. It wasn't.

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: acb 1516 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with AD1981B at irq 17'
   Mixer name : 'Analog Devices AD1981B'
   Components : 'AC97a:41445374'
   Controls : 28
   Simple ctrls : 20
Date: Thu Oct 1 23:40:53 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=UUID=b874d9ac-4415-4b50-b602-0e998443ab63
Lsusb:
 Bus 004 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 003 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: IBM 2371GHG
Package: linux-image-2.6.31-11-generic 2.6.31-11.36
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-11-generic root=UUID=f7788c58-4436-482a-9cd4-299b535b4572 ro quiet splash
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-11-generic N/A
 linux-firmware 1.19
RfKill:

SourcePackage: linux
Tags: kernel-oops
Title: BUG: unable to handle kernel paging request at 0019a8c4
Uname: Linux 2.6.31-11-generic i686
WifiSyslog:
 Oct 2 12:21:49 wolverine NetworkManager: <info> (eth1): supplicant connection state: completed -> group handshake
 Oct 2 12:21:49 wolverine NetworkManager: <info> (eth1): supplicant connection state: group handshake -> completed
 Oct 2 12:27:26 wolverine dhclient: DHCPREQUEST of 10.131.81.40 on eth1 to 192.168.7.30 port 67
 Oct 2 12:27:26 wolverine dhclient: DHCPACK of 10.131.81.40 from 192.168.7.30
 Oct 2 12:27:26 wolverine dhclient: bound to 10.131.81.40 -- renewal in 3009 seconds.
dmi.bios.date: 06/15/2005
dmi.bios.vendor: IBM
dmi.bios.version: 1UETB6WW (1.66 )
dmi.board.name: 2371GHG
dmi.board.vendor: IBM
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: IBM
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371GHG:pvrThinkPadX40:rvnIBM:rn2371GHG:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
dmi.product.name: 2371GHG
dmi.product.version: ThinkPad X40
dmi.sys.vendor: IBM

Andrew Brown (seatrout) wrote :
rohart (rogerivanhart-gmx) wrote :

Reported kernel crash also affects 64bit systems

Philip Muškovac (yofel) on 2009-11-17
summary: - Kernel crash when clicking on crash reporter (!)
+ Kernel crash when clicking on crash reporter (!) - BUG: unable to handle
+ kernel paging request at 0019a8c4
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 430011, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

Changed in linux (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers