This looks like something went bum and caused the kernel to jump to
address zero after waking up while waiting for a buffer to become
unlocked. Looks like an SMP system too, so anything is possible ;)
invalid operand: 0000
CPU: 0
EIP: 0010:[<00000007>]
EFLAGS: 00010e82
eax: 001cb740 ebx: 01637c0c ecx: 001cb740 edx: 001cb740
esi: 001cb740 edi: 00000000 ebp: 01462e8c esp: 01462e68
ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Process rm (pid: 106, process nr: 26, stackpage=01462000)
Stack: 01db9908 01462ea0 fffffc18 001cb740 01db9908 01462ea0 01dde61c 00000202
00000000 01dde61c 001224b5 00000816 001ee35c 01b2dc30 01637c0c 01462ea0
001239ff 01db9908 0001e012 01db9908 00153136 00000816 0001e012 00001000
Call Trace: [<001224b5>] [<001239ff>] [<00153136>] [<00121cf5>] [<00153c03>] [<00129a52>] [<00129c58>]
[<00129cf0>] [<00127fa9>] [<0010a3f9>]
Code: f0 c3 e2 00 f0 fd 00 00 f0 fd 00 00 f0 54 ff 00 f0 fd 00 00
[2(rlk)||{!13}<rlk-ppp-1>/mnt/sandbox4/linux-1.3]
% ksymoops System.map < ../oops.3
Using `System.map' to map addresses to symbols.
Trace: 1224b5 <__wait_on_buffer+91/f0>