kernel BUG at filemap.c:460!
Entering kdb due to panic @ 0xc011dc4e
eax = 0x0000001d ebx = 0xc371bef4 ecx = 0xc371a000 edx = 0x0000003c
esi = 0xc042a064 edi = 0xc042a048 esp = 0xc02466ac eip = 0xc011dc4e
ebp = 0xc371befc ss = 0xc02466a2 cs = 0x00000010 eflags = 0x00010286
ds = 0x00000018 es = 0x00000018 origeax = 0xffffffff
kdb> bt
EBP Caller Function(args)
0xc371bf54 0xc011ea97 ___wait_on_page(0xc042a048)
0xc371bf8c 0xc011eccd do_generic_file_read(0xc3748420, 0xc3748434, 0xc371bf7c, 0xc011ebf0)
0xc371bfbc 0xc01279e8 generic_file_read(0xc3748420, 0x804b478, 0xd80, 0xc3748434)
0xbffff724 0xc0107ca4 sys_read(0x3, 0x804b478, 0xd80, 0x0, 0xa)
kdb> md 0xc042a048
c042a048: 00000000 00000000 c0f0c298 00000000 .........ÂðÀ....
c042a058: 00000000 00000002 00000001 00000000 ................
c042a068: c371beec c371beec c042a070 c02e78b9 ì¾qÃì¾qÃp BÀ¹x.À
c042a078: c0341b68 c26bef80 ffffffff 00000000 h.4À.ïkÂÿÿÿÿ....
c042a088: 00000000 00000000 003a6000 00000000 .........`:.....
c042a098: 00000001 00000008 00000000 c042a0a4 ............¤ BÀ
c042a0a8: c042a0a4 c042a0ac c02e78b9 00000000 ¤ BÀ¬ BÀ¹x.À....
c042a0b8: c30e99e0 00000000 c042a0fc c0429904 à..Ã....ü BÀ..BÀ
kdb> go
Unable to handle kernel NULL pointer dereference at virtual address 00000000
current->tss.cr3 = 03717000, %cr3 = 03717000
*pde = 00000000
Oops: 0002
CPU: 0
EIP: 0010:[___wait_on_page+398/496]
EFLAGS: 00010286
eax: 0000001d ebx: c371bef4 ecx: c371a000 edx: 0000003c
esi: c042a064 edi: c042a048 ebp: c371befc esp: c371beb4
ds: 0018 es: 0018 ss: 0018
Process rwhod (pid: 122, process nr: 19, stackpage=c371b000)
Stack: 000001cc 00000000 c042a048 c2f0e000 00000292 c371a000 01234567 c371a000
00000000 00000000 c371bef4 00000000 01234567 c371a000 c042a068 c042a068
c371bef4 00000000 c371bf54 c011ea97 c042a048 00000d80 0804b478 c3748420
Call Trace: [do_generic_file_read+1799/2144]
[do_no_page+87/240]
[generic_file_read+93/128]
[file_read_actor+0/128]
[sys_read+200/240]
[system_call+52/56]
Code: c7 05 00 00 00 00 00 00 00 00 83 c4 0c e9 73 ff ff ff 8b 7d
Scenario:
Bonnie in same scratch partition
goto laptop and try to rlogin to test box while Bonnie runs..
see Password: and instantly on test box:
bad magic c039e5c0 (should be c371bef4), wq bug, forcing oops.
Entering kdb due to panic @ 0xc010ffbc
eax = 0x00000016 ebx = 0xc371bee4 ecx = 0xc02c3564 edx = 0xc4f54000
esi = 0xc042a070 edi = 0xc01446d3 esp = 0xc024508c eip = 0xc010ffbc
ebp = 0xc35ebf24 ss = 0xc35ea000 cs = 0x00000010 eflags = 0x00010086
ds = 0x00000018 es = 0x00000018 origeax = 0xffffffff
kdb> bt
EBP Caller Function(args)
0xc35ebf60 0xc011fe5a __wake_up()
0xc35ebf80 0xc01446fe generic_file_write(0xc3553020, 0xbfffddc0, 0x180, 0xc3553034, 0xc01446b0)
0xc35ebfbc 0xc0127b35 ext2_file_write(0xc3553020, 0xbfffddc0, 0x180, 0xc3553034)
0xbfffcd54 0xc0107ca4 sys_write(0x3, 0xbfffddc0, 0x180, 0xbfffcbb4, 0xbfffcbb4)
kdb> go
Unable to handle kernel NULL pointer dereference at virtual address 00000000
current->tss.cr3 = 03631000, %cr3 = 03631000
*pde = 00000000
Oops: 0002
CPU: 0
EIP: 0010:[__wake_up+172/240]
EFLAGS: 00010086
eax: 00000016 ebx: c371bee4 ecx: c02c3564 edx: c4f54000
esi: c042a070 edi: c01446d3 ebp: c35ebf24 esp: c35ebf10
ds: 0018 es: 0018 ss: 0018
Process login (pid: 221, process nr: 26, stackpage=c35eb000)
Stack: 00000180 00000180 00000282 c042a068 00000003 c35ebf60 c011fe5a c3553020
c0f0c300 c3553020 00000000 00000000 c042a048 c35ea000 00000d80 00000000
00000000 c0341b68 00000d80 c0f0c298 c35ebf80 c01446fe c3553020 bfffddc0
Call Trace: [generic_file_write+602/720]
[ext2_file_write+30/48]
[ext2_write_one_page+0/48]
[sys_write+293/384]
[ext2_file_write+0/48]
[system_call+52/56]
Code: c7 05 00 00 00 00 00 00 00 00 83 c4 04 8b 53 04 8b 32 85 75
After this oops, can no longer log in. Bonnie is still running,
and running and running, so kill it (works). Attempt to delete
stale Bonnie.xxx file, rm runs and runs and runs... is immortal.
Test-pilot pulls face-curtain.. X-237 auto-lands fully intact ;-)
-Mike
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/