Couls somebody please give me some assistance in working out what
caused these oopses?
They are from a peering news server (diablo 1.15)which was running
with a load of between 30 and 60 at the time, approximatly 100 or
so processes (and simmilar number of open nntp connections) and a
'full' 44000 route routing table learned via iBGP useing gated.
TIA, Robert Collier.
--[ oops 1 ]--
general protection: 0000
CPU: 0
EIP: 0010:[<0013d800>]
EFLAGS: 00010086
eax: 00000001 ebx: fd000000 ecx: 054f69d0 edx: 054f6000
esi: 00000001 edi: 00000202 ebp: 0744ffff esp: 07441ea8
ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Process gated (pid: 88, process nr: 6, stackpage=07441000)
Stack: 00000000 05c28810 00000001 0013dd28 00000000 07441f1c 07441f30 07441f40
01443414 04390003 0013ea73 0000698e 0000ffff 00000000 0d0cc8c3 00000003
ffffffff 0000890c 080bd2f8 07441f70 080bd2a4 07441f20 00000000 0013eafb
Call Trace: [<0013dd28>] [<0013ea73>] [<0013eafb>] [<0015019b>] [<00135b59>] [<0012ca17>] [<0010a655>]
Code: 83 7b 10 00 75 36 8b 53 20 8b 03 89 06 c7 43 20 00 00 00 00
kfree of non-kmalloced memory: 07f91a58, next= 0412e000, order=1
Using `/boot/System.map' to map addresses to symbols.
>>EIP: 13d800 <ip_rt_run_bh+6c/b8>
Trace: 13dd28 <rt_del+168/180>
Trace: 13ea73 <ip_rt_kill+87/9c>
Trace: 13eafb <ip_rt_ioctl+73/a4>
Trace: 15019b <inet_ioctl+2ef/368>
Trace: 135b59 <sock_ioctl+21/28>
Trace: 12ca17 <sys_ioctl+ff/110>
Trace: 10a655 <system_call+55/80>
Code: 13d800 <ip_rt_run_bh+6c/b8>
Code: 13d800 <ip_rt_run_bh+6c/b8> 83 7b 10 00 cmpl $0x0,0x10(%ebx)
Code: 13d804 <ip_rt_run_bh+70/b8> 75 36 jne 13d83c <ip_rt_run_bh+a8/b8>
Code: 13d806 <ip_rt_run_bh+72/b8> 8b 53 20 movl 0x20(%ebx),%edx
Code: 13d809 <ip_rt_run_bh+75/b8> 8b 03 movl (%ebx),%eax
Code: 13d811 <ip_rt_run_bh+7d/b8> 89 06 movl %eax,(%esi)
Code: 13d813 <ip_rt_run_bh+7f/b8> c7 43 20 00 00 movl $0x0,0x20(%ebx)
Code: 13d818 <ip_rt_run_bh+84/b8> 00 00
Code: 13d820 <ip_rt_run_bh+8c/b8>
--[ end oops ]--
--[ oops 2 ]--
general protection: 0000
CPU: 0
EIP: 0010:[<0013d934>]
EFLAGS: 00010086
eax: 00000003 ebx: fd000000 ecx: 04441750 edx: 04441000
esi: 00000001 edi: 001d5b3c ebp: 00000100 esp: 06c0df48
ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Process dnewslink (pid: 17213, process nr: 82, stackpage=06c0d000)
Stack: 00000000 004b12c2 00000000 06c0dfa0 001d5b3c 004b12c2 00000246 0014c318
001b4610 00000000 0014c2f8 00000000 06c0dfa0 0014a28a 004b12c2 001124f1
00000000 00000001 ffffffff 00000001 00000000 06c0dfbc 001ccdc0 00117d0b
Call Trace: [<0014c318>] [<0014c2f8>] [<0014a28a>] [<001124f1>] [<00117d0b>] [<0010a5db>]
Code: 83 7b 10 00 75 36 8b 53 20 8b 03 89 06 c7 43 20 00 00 00 00
Aiee, killing interrupt handler
eth1: trigger_send() called with the transmitter busy.
Using `/boot/System.map' to map addresses to symbols.
>>EIP: 13d934 <ip_rt_check_expire+e8/150>
Trace: 14c318 <arp_check_expire+20/170>
Trace: 14c318 <arp_check_expire+20/170>
Trace: 14a28a <tcp_delack_timer+a/10>
Trace: 1124f1 <timer_bh+2ed/334>
Trace: 117d0b <do_bottom_half+3b/60>
Trace: 10a5db <handle_bottom_half+b/20>
Code: 13d934 <ip_rt_check_expire+e8/150>
Code: 13d934 <ip_rt_check_expire+e8/150> 83 7b 10 00 cmpl $0x0,0x10(%ebx)
Code: 13d938 <ip_rt_check_expire+ec/150> 75 36 jne 13d970 <ip_rt_check_expire+124/150>
Code: 13d93a <ip_rt_check_expire+ee/150> 8b 53 20 movl 0x20(%ebx),%edx
Code: 13d93d <ip_rt_check_expire+f1/150> 8b 03 movl (%ebx),%eax
Code: 13d945 <ip_rt_check_expire+f9/150> 89 06 movl %eax,(%esi)
Code: 13d947 <ip_rt_check_expire+fb/150> c7 43 20 00 00 movl $0x0,0x20(%ebx)
Code: 13d94c <ip_rt_check_expire+100/150> 00 00
Code: 13d954 <ip_rt_check_expire+108/150>
--[ end oops ]--
-- Robert Collier (rrc@bofh.org.uk, rune@ftech.net)"...by God I *KNOW* what this network is for, and you can't have it." --Russ Allbery
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu