BUG: unable to handle kernel paging request at ffff8801ff040000
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
My server running Ubuntu Server 10.04.1 crashed today and when I checked the syslog, this was the last output before the crash:
Sep 10 03:15:04 eridanos kernel: [27981.430032] BUG: unable to handle kernel paging request at ffff8801ff040000
Sep 10 03:15:04 eridanos kernel: [27981.430665] IP: [<ffffffff81130
Sep 10 03:15:04 eridanos kernel: [27981.431101] PGD 1002063 PUD f067 PMD 1000000ffcc0160
Sep 10 03:15:04 eridanos kernel: [27981.431648] Oops: 0000 [#1] SMP
Sep 10 03:15:04 eridanos kernel: [27981.432015] last sysfs file: /sys/devices/
Sep 10 03:15:04 eridanos kernel: [27981.432408] CPU 2
Sep 10 03:15:04 eridanos kernel: [27981.432620] Modules linked in: ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack ipt_REJECT xt_tcpudp iptable_filter ip_tables x_tables kvm_amd kvm bridge stp fbcon tileblit font bitblit softcursor vga16fb vgastate amd64_edac_mod shpchp psmouse serio_raw edac_core k8temp edac_mce_amd i2c_nforce2 lp parport usbhid hid dm_raid45 xor tg3 pata_amd sata_nv forcedeth
Sep 10 03:15:04 eridanos kernel: [27981.437992] Pid: 54, comm: ksmd Not tainted 2.6.32-24-server #42-Ubuntu Sun Fire X2200 M2
Sep 10 03:15:04 eridanos kernel: [27981.438612] RIP: 0010:[<
Sep 10 03:15:04 eridanos kernel: [27981.439198] RSP: 0018:ffff88011a
Sep 10 03:15:04 eridanos kernel: [27981.439467] RAX: 00000001f4db9000 RBX: ffffea0006d90078 RCX: 0000000000001000
Sep 10 03:15:04 eridanos kernel: [27981.439467] RDX: ffff88011adba000 RSI: ffff8801f4db9000 RDI: ffff8801ff040000
Sep 10 03:15:04 eridanos kernel: [27981.439467] RBP: ffff88011adbbdb0 R08: 6db6db6db6db6db7 R09: 0000160000000000
Sep 10 03:15:04 eridanos kernel: [27981.439467] R10: ffffea0006fc8e00 R11: 0000000000000000 R12: ffff88011adbbe10
Sep 10 03:15:04 eridanos kernel: [27981.439467] R13: ffff88021a3709b0 R14: ffff8802029c79c0 R15: ffff8801f829f680
Sep 10 03:15:04 eridanos kernel: [27981.439467] FS: 00007f88f6b1d76
Sep 10 03:15:04 eridanos kernel: [27981.439467] CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
Sep 10 03:15:04 eridanos kernel: [27981.439467] CR2: ffff8801ff040000 CR3: 0000000202b55000 CR4: 00000000000006e0
Sep 10 03:15:04 eridanos kernel: [27981.445706] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Sep 10 03:15:04 eridanos kernel: [27981.445706] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Sep 10 03:15:04 eridanos kernel: [27981.445706] Process ksmd (pid: 54, threadinfo ffff88011adba000, task ffff88011adb16f0)
Sep 10 03:15:04 eridanos kernel: [27981.445706] Stack:
Sep 10 03:15:04 eridanos kernel: [27981.445706] ffff88011adbbe00 ffffffff81130c35 ffff88011adbbe00 ffff88021a3709a8
Sep 10 03:15:04 eridanos kernel: [27981.445706] <0> ffff88011adbbdf0 ffff8801f829f680 ffffea0006d90078 0000000000000000
Sep 10 03:15:04 eridanos kernel: [27981.445706] <0> ffff88011adbbe10 ffff88011ba716f0 ffff88011adbbe40 ffffffff811310c6
Sep 10 03:15:04 eridanos kernel: [27981.445706] Call Trace:
Sep 10 03:15:04 eridanos kernel: [27981.445706] [<ffffffff81130
Sep 10 03:15:04 eridanos kernel: [27981.661368] [<ffffffff81131
Sep 10 03:15:04 eridanos kernel: [27981.672681] [<ffffffff81131
Sep 10 03:15:04 eridanos kernel: [27981.680050] [<ffffffff81131
Sep 10 03:15:04 eridanos kernel: [27981.704891] [<ffffffff81085
Sep 10 03:15:04 eridanos kernel: [27981.720025] [<ffffffff81131
Sep 10 03:15:04 eridanos kernel: [27981.733382] [<ffffffff81084
Sep 10 03:15:04 eridanos kernel: [27981.744587] [<ffffffff81014
Sep 10 03:15:04 eridanos kernel: [27981.762082] [<ffffffff81084
Sep 10 03:15:04 eridanos kernel: [27981.770038] [<ffffffff81014
Sep 10 03:15:04 eridanos kernel: [27981.780025] Code: 8d 04 0f 4b 8d 3c 0a 48 c1 f8 03 48 c1 ff 03 49 0f af c0 49 0f af f8 48 c1 e0 0c 48 8d 34 08 48 c1 e7 0c 48 01 cf b9 00 10 00 00 <f3> a6 0f 97 c0 0f 92 c1 28 c8 0f be c0 83 6a 1c 01 83 6a 1c 01
Sep 10 03:15:04 eridanos kernel: [27981.830022] RIP [<ffffffff81130
Sep 10 03:15:04 eridanos kernel: [27981.840025] RSP <ffff88011adbbdb0>
Sep 10 03:15:04 eridanos kernel: [27981.860024] CR2: ffff8801ff040000
Sep 10 03:15:04 eridanos kernel: [27981.886833] ---[ end trace 516c05170132dd69 ]---
Sep 10 03:15:04 eridanos kernel: [27981.900049] note: ksmd[54] exited with preempt_count 2
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-
Regression: No
Reproducible: No
ProcVersionSign
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
AplayDevices: Error: [Errno 2] No such file or directory
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
Date: Fri Sep 10 11:16:33 2010
Frequency: This has only happened once.
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/
ProcEnviron:
LANG=en_AU.UTF-8
SHELL=/bin/bash
SourcePackage: linux
dmi.bios.date: 02/04/2009
dmi.bios.vendor: Sun Microsystems
dmi.bios.version: S39_3B27
dmi.board.
dmi.board.name: S39
dmi.board.vendor: Sun Microsystems
dmi.board.version: Rev 50
dmi.chassis.
dmi.chassis.type: 23
dmi.chassis.vendor: Sun Microsystems
dmi.chassis.
dmi.modalias: dmi:bvnSunMicro
dmi.product.name: Sun Fire X2200 M2
dmi.product.
dmi.sys.vendor: Sun Microsystems
Hi Tomas,
If you could also please 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/KernelMainl ineBuilds . 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.
[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]