kernel BUG at /build/buildd/linux- 2.6.32/kernel/cred.c:168
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux |
Expired
|
High
|
|||
linux (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
The server locked up at the console (no response even to sysrq+space). Shortly beforehand the serial console displayed the message:
Jul 17 01:15:07 byron kernel: [372978.128744] ------------[ cut here ]------------
Jul 17 01:15:07 byron kernel: [372978.144685] kernel BUG at /build/
Jul 17 01:15:07 byron kernel: [372978.162519] invalid opcode: 0000 [#4] SMP
Jul 17 01:15:07 byron kernel: [372978.177710] last sysfs file: /sys/devices/
Jul 17 01:15:07 byron kernel: [372978.206877] CPU 13
Jul 17 01:15:07 byron kernel: [372978.219599] 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_intel kvm 8021q garp nfsd exportfs nfs lockd nfs_acl auth_rpcgss sunrpc fbcon tileblit font bridge bitblit stp softcursor vga16fb vgastate ipmi_si ipmi_devintf ioatdma ipmi_msghandler psmouse serio_raw joydev usbhid hid 3w_9xxx igb dca
Jul 17 01:15:07 byron kernel: [372978.238027] Pid: 25258, comm: munin-node Tainted: G D 2.6.32-23-server #37-Ubuntu X8DTU
Jul 17 01:15:07 byron kernel: [372978.238030] RIP: 0010:[<
Jul 17 01:15:07 byron kernel: [372978.238040] RSP: 0018:ffff8802af
Jul 17 01:15:07 byron kernel: [372978.238043] RAX: 0000000000000001 RBX: ffff880c1e99e6c0 RCX: 00000000ffffffff
Jul 17 01:15:07 byron kernel: [372978.238045] RDX: 00000000ffffffff RSI: ffff880c1e99e6c0 RDI: ffff880c1e99e6c0
Jul 17 01:15:07 byron kernel: [372978.238051] RBP: ffff8802afb27ed8 R08: 0000000000000000 R09: ffff880b5de51680
Jul 17 01:15:07 byron kernel: [372978.238054] R10: 00000000000000c0 R11: 0000000000000000 R12: ffff880c1e99f8c0
Jul 17 01:15:07 byron kernel: [372978.238056] R13: ffff880253f20000 R14: 0000000000000001 R15: 0000000000000001
Jul 17 01:15:07 byron kernel: [372978.238059] FS: 00007f8d7244670
Jul 17 01:15:07 byron kernel: [372978.238062] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 17 01:15:07 byron kernel: [372978.238064] CR2: 00007f8d71545240 CR3: 0000000253fdc000 CR4: 00000000000026e0
Jul 17 01:15:07 byron kernel: [372978.238067] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Jul 17 01:15:07 byron kernel: [372978.238069] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Jul 17 01:15:07 byron kernel: [372978.238072] Process munin-node (pid: 25258, threadinfo ffff8802afb26000, task ffff880253f20000)
Jul 17 01:15:07 byron kernel: [372978.238074] Stack:
Jul 17 01:15:07 byron kernel: [372978.238075] ffff8802afb27f08 ffffffff8108bb01 ffff8802afb27f08 ffff880c1e99f8c0
Jul 17 01:15:07 byron kernel: [372978.238078] <0> ffff880c1e99ee40 0000000000000001 ffff8802afb27f38 ffffffff8108cbb1
Jul 17 01:15:07 byron kernel: [372978.238082] <0> 0000000000000001 0000000001a2a960 0000000001a2a960 ffff880c1e99ee40
Jul 17 01:15:07 byron kernel: [372978.238085] Call Trace:
Jul 17 01:15:07 byron kernel: [372978.238090] [<ffffffff8108b
Jul 17 01:15:07 byron kernel: [372978.238094] [<ffffffff8108c
Jul 17 01:15:07 byron kernel: [372978.238098] [<ffffffff8108c
Jul 17 01:15:07 byron kernel: [372978.238106] [<ffffffff81013
Jul 17 01:15:07 byron kernel: [372978.238108] Code: 8b 04 25 c0 cb 00 00 48 3b b8 50 04 00 00 74 23 48 3b b8 48 04 00 00 74 16 48 83 ef 80 48 c7 c6 f0 b4 08 81 e8 04 e8 03 00 c9 c3 <0f> 0b eb fe 0f 0b eb fe 0f 0b eb fe 66 0f 1f 44 00 00 55 48 89
Jul 17 01:15:07 byron kernel: [372978.238129] RIP [<ffffffff8108b
Jul 17 01:15:07 byron kernel: [372978.238132] RSP <ffff8802afb27ed8>
Jul 17 01:15:07 byron kernel: [372978.245944] ---[ end trace 10ea347dd48afe27 ]---
Kernel version: Linux byron 2.6.32-23-server #37-Ubuntu SMP Fri Jun 11 09:11:11 UTC 2010 x86_64 GNU/Linux
The same bug appears to be known to redhat and they propose a fix.
https:/
---
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
DistroRelease: Ubuntu 10.04
Frequency: Once every few weeks.
InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 (20100427)
MachineType: Supermicro X8DTU
Package: linux (not installed)
PciMultimedia:
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
Regression: No
Reproducible: No
Tags: lucid kconfig needs-upstream-
Uname: Linux 2.6.32-24-server x86_64
UserGroups:
dmi.bios.date: 03/01/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.1a
dmi.board.
dmi.board.name: X8DTU
dmi.board.vendor: Supermicro
dmi.board.version: 1234567890
dmi.chassis.
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: X8DTU
dmi.product.
dmi.sys.vendor: Supermicro
Changed in linux: | |
status: | Unknown → Confirmed |
Changed in linux: | |
importance: | Unknown → High |
Changed in linux: | |
status: | Confirmed → Expired |
Hi Anthony,
Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http:// cdimage. ubuntu. com/daily/ current/ . If the issue remains, please run the following command from a Terminal (Applications- >Accessories- >Terminal) . It will automatically gather and attach updated debug information to this report.
apport-collect -p linux 606892
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/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.]