Kernel Oops - BUG: unable to handle kernel paging request at ffff8801ff040000; RIP: 0010:[<ffffffff8113091e>] [<ffffffff8113091e>] memcmp_pages+0x6e/0x90

Bug #635667 reported by Tomas Cassidy
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Found this crash log in /var/crash

ProblemType: KernelOops
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-24-server 2.6.32-24.42
Regression: No
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.32-24.42-server 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-server x86_64
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory
Annotation: Your system might become unstable now and might need to be restarted.
AplayDevices: Error: [Errno 2] No such file or directory
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
Date: Fri Sep 10 22:41:43 2010
Failure: oops
Frequency: I don't know.
Lsusb:
 Bus 002 Device 004: ID 046d:c303 Logitech, Inc. iTouch Keyboard
 Bus 002 Device 003: ID 046d:0b01 Logitech, Inc.
 Bus 002 Device 002: ID 0b38:0003
 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: Sun Microsystems Sun Fire X2200 M2
PciMultimedia:

ProcCmdLine: root=/dev/mapper/nvidia_idbfeifi1 ro quiet splash
SourcePackage: linux
Title: BUG: unable to handle kernel paging request at ffff8801ff040000
dmi.bios.date: 02/04/2009
dmi.bios.vendor: Sun Microsystems
dmi.bios.version: S39_3B27
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: S39
dmi.board.vendor: Sun Microsystems
dmi.board.version: Rev 50
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 23
dmi.chassis.vendor: Sun Microsystems
dmi.chassis.version: Rev 50
dmi.modalias: dmi:bvnSunMicrosystems:bvrS39_3B27:bd02/04/2009:svnSunMicrosystems:pnSunFireX2200M2:pvrRev50:rvnSunMicrosystems:rnS39:rvrRev50:cvnSunMicrosystems:ct23:cvrRev50:
dmi.product.name: Sun Fire X2200 M2
dmi.product.version: Rev 50
dmi.sys.vendor: Sun Microsystems

Revision history for this message
Tomas Cassidy (tomas-cassidy) wrote :
tags: added: kj-triage
Brad Figg (brad-figg)
tags: added: acpi-method-return
tags: added: acpi-table-checksum
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Tomas Cassidy, thank you for reporting this bug and helping make Ubuntu better. This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in the development release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

summary: - BUG: unable to handle kernel paging request at ffff8801ff040000
+ Kernel Oops - BUG: unable to handle kernel paging request at
+ ffff8801ff040000; RIP: 0010:[<ffffffff8113091e>] [<ffffffff8113091e>]
+ memcmp_pages+0x6e/0x90
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.