kernel BUG at vmscan.c:359!
invalid operand: 0000
CPU: 0
EIP: 0010:[shrink_cache+192/784] Not tainted
EIP: 0010:[<c012b940>] Not tainted
EFLAGS: 00010202
eax: 010000cc ebx: c17a6000 ecx: c19c033c edx: c1c34000
esi: c19c0320 edi: 0000001e ebp: 00005041 esp: c1c35f34
ds: 0018 es: 0018 ss: 0018
Process kswapd (pid: 4, stackpage=c1c35000)
Stack: 00000000 c1c34000 00000200 000001d0 c02754e0 c1c0d198 d075fcc0 c1c0dae0
00000001 00000020 000001d0 00000006 00000020 c012bce0 00000006 0000000b
c02754e0 00000006 000001d0 c02754e0 00000000 c012bd4c 00000020
c02754e0 Call Trace: [shrink_caches+80/128] [try_to_free_pages_zone+60/96]
[kswapd_balance_pgdat+79/160] [kswapd_balance+38/64] [kswapd+161/192]
Call Trace: [<c012bce0>] [<c012bd4c>] [<c012be5f>] [<c012bed6>] [<c012c011>]
[kswapd+0/192] [_stext+0/48] [kernel_thread+38/48] [kswapd+0/192]
[<c012bf70>] [<c0105000>] [<c0107116>] [<c012bf70>]
Code: 0f 0b 67 01 a6 3d 24 c0 8b 01 8b 51 04 31 db 89 50 04 89 02
>> EIP; c012b940 <shrink_cache+c0/310> <=====
Trace; c012bce0 <shrink_caches+50/80>
Trace; c012bd4c <try_to_free_pages_zone+3c/60>
Trace; c012be5e <kswapd_balance_pgdat+4e/a0>
Trace; c012bed6 <kswapd_balance+26/40>
Trace; c012c010 <kswapd+a0/c0>
Trace; c012bf70 <kswapd+0/c0>
Trace; c0105000 <_stext+0/0>
Trace; c0107116 <kernel_thread+26/30>
Trace; c012bf70 <kswapd+0/c0>
Code; c012b940 <shrink_cache+c0/310>
00000000 <_EIP>:
Code; c012b940 <shrink_cache+c0/310> <=====
0: 0f 0b ud2a <=====
Code; c012b942 <shrink_cache+c2/310>
2: 67 01 a6 3d 24 addr16 add %esp,9277(%bp)
Code; c012b946 <shrink_cache+c6/310>
7: c0 8b 01 8b 51 04 31 rorb $0x31,0x4518b01(%ebx)
Code; c012b94e <shrink_cache+ce/310>
e: db 89 50 04 89 02 (bad) 0x2890450(%ecx)
The system was under minimal load at the time (xmms, StarOffice, gaim) and
does not use either the netdump or O_STREAMING patches that were used in the
original post. The system has successfully passed several hours of memtest86.
Also, when I rebooted, ext3 declared that it was "recovering journal" on my
/home filesystem if that's of any consequence.
Please CC me on any replies, thanks!
Oh, and the original reporter has stated that moving to 2.4.21-pre5aa2 seems
to have cured him of this problem.
______________________________________
Andrew Ferguson - owsla@princeton.edu
http://www.princeton.edu/~owsla/
http://www.phstower.org/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/