[Bug 18298] New: kernel BUG followed by a machine crash
bugzilla-daemon at bugzilla.ubuntu.com
bugzilla-daemon at bugzilla.ubuntu.com
Sat Oct 22 16:57:26 UTC 2005
Please do not reply to this email. You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=18298
Ubuntu | linux
Summary: kernel BUG followed by a machine crash
Product: Ubuntu
Version: unspecified
Platform: i386
OS/Version: other
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: linux
AssignedTo: ben.collins at ubuntu.com
ReportedBy: marius at pov.lt
QAContact: kernel-bugs at lists.ubuntu.com
I was copying a bunch of files from a DVD to my home fileserver over
Samba (GNOME won't let me mount NFS shares, so I have to use Samba).
Suddenly the server crashed -- no pings, no disk activity. Since I have
no easily-available spare monitor, I just hit the Reset button and went
on with my life.
The server runs Ubuntu Hoary and has a 2.6.10-5-686 kernel (2.6.10-34.7).
It has two RAID-1 devices on two 250-gig IDE disks. As far as I can
tell, one of them uses the md driver, while the other uses evms. Don't
ask me why.
The server crashed at 18:50:10 (according to timestamps in log files)
and came up at 18:58. I also found this in kern.log:
Oct 22 18:31:58 localhost kernel: ------------[ cut here ]------------
Oct 22 18:31:58 localhost kernel: kernel BUG at mm/rmap.c:483!
Oct 22 18:31:58 localhost kernel: invalid operand: 0000 [#1]
Oct 22 18:31:58 localhost kernel: PREEMPT
Oct 22 18:31:58 localhost kernel: Modules linked in: nfsd exportfs lockd sunrpc
af_packet ipv6 ip_nat_irc ip_conntrack_irc ip_nat_ftp ip_conntrack_ftp ipt_state
ipt_LOG ipt_limit iptable_nat ip_conntrack iptable_filter ip_tables ne2k_pci
8390 via_rhine mii i2c_piix4 i2c_core uhci_hcd usbcore pci_hotplug intel_agp
agpgart pcspkr rtc dm_mod evdev capability commoncap psmouse mousedev parport_pc
lp parport ide_cd cdrom ext3 jbd mbcache ide_generic piix ide_disk ide_core
raid1 md unix thermal processor fan fbcon font bitblit vesafb cfbcopyarea
cfbimgblt cfbfillrect
Oct 22 18:31:58 localhost kernel: CPU: 0
Oct 22 18:31:58 localhost kernel: EIP: 0060:[page_remove_rmap+43/63] Not
tainted VLI
Oct 22 18:31:58 localhost kernel: EFLAGS: 00010282 (2.6.10-5-686)
Oct 22 18:31:58 localhost kernel: EIP is at page_remove_rmap+0x2b/0x3f
Oct 22 18:31:58 localhost kernel: eax: fffffff8 ebx: 0003b000 ecx: c10695c0
edx: c10695c0
Oct 22 18:31:58 localhost kernel: esi: cc16f490 edi: c10695c0 ebp: 0003e000
esp: cc889e88
Oct 22 18:31:58 localhost kernel: ds: 007b es: 007b ss: 0068
Oct 22 18:31:58 localhost kernel: Process mlnet (pid: 4487, threadinfo=cc888000
task=cc8b55e0)
Oct 22 18:31:58 localhost kernel: Stack: c0143978 c10695c0 00000000 c645a080
c0e4a81e 034ae067 b80e9000 cc05bb80
Oct 22 18:31:58 localhost kernel: b7d27000 00000000 c0143ade c0371cf4
cc05bb7c b7ce9000 0003e000 00000000
Oct 22 18:31:58 localhost kernel: c0371cf4 b7ce9000 cc05bb80 b7d27000
00000000 c0143b45 c0371cf4 cc05bb7c
Oct 22 18:31:58 localhost kernel: Call Trace:
Oct 22 18:31:58 localhost kernel: [zap_pte_range+305/576] zap_pte_range+0x131/0x240
Oct 22 18:31:58 localhost kernel: [zap_pmd_range+87/115] zap_pmd_range+0x57/0x73
Oct 22 18:31:58 localhost kernel: [unmap_page_range+75/113]
unmap_page_range+0x4b/0x71
Oct 22 18:31:58 localhost kernel: [unmap_vmas+248/438] unmap_vmas+0xf8/0x1b6
Oct 22 18:31:58 localhost kernel: [unmap_region+123/230] unmap_region+0x7b/0xe6
Oct 22 18:31:58 localhost kernel: [do_munmap+299/383] do_munmap+0x12b/0x17f
Oct 22 18:31:58 localhost kernel: [sys_munmap+80/116] sys_munmap+0x50/0x74
Oct 22 18:31:58 localhost kernel: [sysenter_past_esp+82/117]
sysenter_past_esp+0x52/0x75
Oct 22 18:31:58 localhost kernel: Code: 8b 54 24 04 8b 02 f6 c4 08 75 2a 83 42
08 ff 0f 98 c0 84 c0 74 14 8b 42 08 83 c0 01 78 0d 9c 58 fa 83 2d b0 f4 37 c0 01
50 9d c3 <0f> 0b e3 01 ef f4 29 c0 eb e9 0f 0b e0 01 ef f4 29 c0 eb cc 55
Oct 22 18:31:58 localhost kernel: <6>note: mlnet[4487] exited with preempt_count 1
Oct 22 18:31:58 localhost kernel: scheduling while atomic: mlnet/0x00000001/4487
Oct 22 18:31:58 localhost kernel: [schedule+1327/1332] schedule+0x52f/0x534
Oct 22 18:31:58 localhost kernel: [complement_pos+32/387] complement_pos+0x20/0x183
Oct 22 18:31:58 localhost kernel: [rwsem_down_read_failed+143/380]
rwsem_down_read_failed+0x8f/0x17c
Oct 22 18:31:58 localhost kernel: [.text.lock.futex+7/218]
.text.lock.futex+0x7/0xda
Oct 22 18:31:58 localhost kernel: [do_futex+100/156] do_futex+0x64/0x9c
Oct 22 18:31:58 localhost kernel: [sys_futex+236/248] sys_futex+0xec/0xf8
Oct 22 18:31:58 localhost kernel: [mm_release+154/162] mm_release+0x9a/0xa2
Oct 22 18:31:58 localhost kernel: [do_exit+179/1143] do_exit+0xb3/0x477
Oct 22 18:31:58 localhost kernel: [do_invalid_op+0/195] do_invalid_op+0x0/0xc3
Oct 22 18:31:58 localhost kernel: [do_trap+0/272] do_trap+0x0/0x110
Oct 22 18:31:58 localhost kernel: [do_invalid_op+174/195] do_invalid_op+0xae/0xc3
Oct 22 18:31:58 localhost kernel: [free_hot_cold_page+172/259]
free_hot_cold_page+0xac/0x103
Oct 22 18:31:58 localhost kernel: [timer_interrupt+298/313]
timer_interrupt+0x12a/0x139
Oct 22 18:31:58 localhost kernel: [page_remove_rmap+43/63]
page_remove_rmap+0x2b/0x3f
Oct 22 18:31:58 localhost kernel: [__do_softirq+126/135] __do_softirq+0x7e/0x87
Oct 22 18:31:58 localhost kernel: [error_code+43/48] error_code+0x2b/0x30
Oct 22 18:31:58 localhost kernel: [page_remove_rmap+43/63]
page_remove_rmap+0x2b/0x3f
Oct 22 18:31:58 localhost kernel: [zap_pte_range+305/576] zap_pte_range+0x131/0x240
Oct 22 18:31:58 localhost kernel: [zap_pmd_range+87/115] zap_pmd_range+0x57/0x73
Oct 22 18:31:58 localhost kernel: [unmap_page_range+75/113]
unmap_page_range+0x4b/0x71
Oct 22 18:31:58 localhost kernel: [unmap_vmas+248/438] unmap_vmas+0xf8/0x1b6
Oct 22 18:31:58 localhost kernel: [unmap_region+123/230] unmap_region+0x7b/0xe6
Oct 22 18:31:58 localhost kernel: [do_munmap+299/383] do_munmap+0x12b/0x17f
Oct 22 18:31:58 localhost kernel: [sys_munmap+80/116] sys_munmap+0x50/0x74
Oct 22 18:31:58 localhost kernel: [sysenter_past_esp+82/117]
sysenter_past_esp+0x52/0x75
There are no other suspicious tracebacks in the log files, which go back
all the way to the installation of the thing (September 18). There were
two or three other suspicious crashes that I attributed to momentary
power losses. The server was running Debian before I bought two new
disks and installed Ubuntu on them.
--
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
More information about the kernel-bugs
mailing list