Kernel OOPS with 1.2.11

Daniel Hollis (
Mon, 24 Jul 1995 20:59:52 -0700 (PDT)

Here's the latest crash:

rs_multi loop break
general protection: 0000
EIP: 0010:0017e87e
EFLAGS: 00010202
eax: 8117e6ff ebx: 00009097 ecx: 0019b558 edx: 0000030f
esi: 0019b558 edi: 0000030f ebp: 00000001 esp: 00a70d8c
ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Process lynx (pid: 9919, process nr: 69, stackpage=00a70000)
Stack: 00194750 0071d6fc 00000000 00000001 00000000 00000001 00000036 00000300
00136f6b 0071d6fc 0019b558 0019b558 024e916c 024e916c 0071d6fc 00000246
0013d36d 0071d6fc 0019b558 00000001 024e9114 0019c05c 0019c05c 00000000
Call Trace: 00136f6b 0013d36d 0013d54a 0013736b 0011c74e 001106ad 001308c6
00130a0c 001347c8 00110729
Code: 24 18 83 fd 3c 7d 05 bd 3c 00 00 00 f6 43 10 20 0f 84 d4 01
Aiee, killing interrupt handler

0017e708 t _ei_start_xmit <- Crash! 17e87e
00136d70 T _dev_queue_xmit <- 136f6b
0013d124 t _ip_forward <- 13d36d
0013d384 T _ip_rcv <- 13d54a
00137270 T _net_bh <- 13736b
0011c710 T _do_bottom_half <- 11c74e
001106a0 t handle_bottom_half <- 1106ad
001308ac t ___get_fd_set <- 1308c6
0013093c T _sys_select <- 130a0c
001346e0 T _sys_socketcall <- 1347c8
001106d0 T _system_call <- 110729

System wasn't hung when I got to the console, although it might as well
have been. System was incredibly slow, took >4 minutes to login (approx.
20-30 seconds to respond to keystrokes). Switching consoles appeared to be
lagged by a fraction of a second or so.. where normally it's instantaneous.

Got to the command prompt after 10 minutes, but it never responded to the
three finger salute... so I ended up hitting the reset button.

Linux 1.2.11 with 1.3.5 8390.c as suggested (made no difference, really).

Hardware configuration:

DX4/100, 40mb RAM

NE2000 card:
eth0 Link encap:10Mbps Ethernet HWaddr 00:00:B4:64:4E:F9
inet addr: Bcast: Mask:
RX packets:2593 errors:0 dropped:0 overruns:0
TX packets:3018 errors:0 dropped:0 overruns:0
Interrupt:10 Base address:0x300

2 BOCA2016's, one at 0x100 IRQ 12, the other at 0x200 IRQ 15.
Buslogic at 0x330 IRQ 11 BIOS 0xDC000

Could someone PLEASE look at this?

We'll may be trying an SMC Ultra card if we can get our hands on one, and
see if that makes any difference. Will the SMC prove anything or should we
try some other card to rule out our hardware and definitively point the
finger at the Linux networking code? What do we have to do to satisfy the
kernel developers that it's not our hardware? What card will prove it?

I still have all the previous kernel panic messages saved so if someone
wants to see the pattern of crashes we're having, I can dig them up again.

Dan Hollis | Seiyuu Daisuki! |"Ranko-chan, ii oyome-san
MAGICK.NET System Administrator | Orikasa Ai | ni nareru wa yo" - | Yokoyama Chisa | Saotome Nodoka | ("(^_^)") |