Repeatable network oops

Matthew Harrell (mharrell@erols.com)
Fri, 22 Nov 1996 18:58:39 -0500 (EST)

I've been able to repeatable produce this oops in 2.1.12 with any network
behaviour from my computer. The computer is a laptop with a 3c562 pcmcia
card, pcmcia 2.8.23 w/ the 2.1.? patch, and libc 5.4.12. Here's the
oops and ksymoops output:

Unable to handle kernel NULL pointer dereference at virtual address 00000000
current->tss.cr3 = 00972000, ^Tr3 = 00972000
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<c2840d25>]
EFLAGS: 00010212
eax: 00000000 ebx: 00000300 ecx: 00000001 edx: 00000300
esi: 00000000 edi: 00000300 ebp: c0772b10 esp: c0772ae8
ds: 0018 es: 0018 ss: 0018
Process ping (pid: 452, process nr: 10, stackpage=c0772000)
Stack: 00000000 c07f5438 c07f51a0 00000000 00000000 00000000 00000246 c05b8798
0000002a c008b218 c07f5114 c013cb10 c07f5438 c07f5114 c07f5428 0101a8c0
c07f5114 c07f5438 00000000 00000246 c013cb5a c07f5438 c07f5114 00000000
Call Trace: [<c013cb10>] [<c013cb5a>] [<c0152d39>] [<c013ef30>] [<c01521f5>] [<c01527be>] [<c013f249>]
[<c0142e61>] [<c0143260>] [<c0110378>] [<c011b191>] [<c0143371>] [<c0147825>] [<c013306d>] [<c01504aa>]
[<c0150628>] [<c01506a4>] [<c01558c5>] [<c0139c66>] [<c017ec85>] [<c0180a24>] [<c013a9a3>] [<c0182ad6>]
[<c0182a6f>] [<c017e0eb>] [<c017a1fd>] [<c010a8c8>]
Code: f3 6f a1 10 89 1b c0 8b 55 0c 89 42 30 89 f9 66 83 c1 0c 89
Aiee, killing interrupt handler

Using `/boot/System.map-2.1.12' to map addresses to symbols.

Trace: c013cb10 <do_dev_queue_xmit+194/1c4>
Trace: c013cb5a <dev_queue_xmit+1a/24>
Trace: c0152d39 <arp_send+215/220>
Trace: c013ef30 <eth_header>
Trace: c01521f5 <arp_new_entry+bd/f4>
Trace: c01527be <arp_bind_cache+3be/4b0>
Trace: c013f249 <eth_header_cache_bind+41/70>
Trace: c0142e61 <rt_cache_add+6d/16c>
Trace: c0143260 <ip_rt_slow_route+300/394>
Trace: c0110378 <do_page_fault+118/2f4>
Trace: c011b191 <do_mmap+341/39c>
Trace: c0143371 <ip_rt_route+71/78>
Trace: c0147825 <ip_build_xmit+195/db8>
Trace: c013306d <load_elf_binary+b85/c20>
Trace: c01504aa <raw_sendto+176/188>
Trace: c0150628 <raw_getfrag>
Trace: c01506a4 <raw_sendmsg+34/e8>
Trace: c01558c5 <inet_sendmsg+91/a8>
Trace: c0139c66 <sys_sendto+1b6/1d0>
Trace: c017ec85 <scrup+1e5/29c>
Trace: c0180a24 <do_con_write+6a0/18b8>
Trace: c013a9a3 <sys_socketcall+487/6d4>
Trace: c0182ad6 <con_put_char+1e/28>
Trace: c0182a6f <con_flush_chars+1f/24>
Trace: c017e0eb <write_chan+133/1b4>
Trace: c017a1fd <tty_write+dd/130>
Trace: c010a8c8 <system_call+38/40>

Code: repz outsl %ds:(%esi),(%dx)
Code: movl 0xc01b8910,%eax
Code: movl 0xc(%ebp),%edx
Code: movl %eax,0x30(%edx)
Code: movl %edi,%ecx
Code: addw $0xc,%cx
Code: movl %eax,(%eax)
Code: nop
Code: nop
Code: nop

Am I the only person who has been having serious network problems since
2.1.7?

-- 
  Matthew Harrell                          I used to have a handle on life,
  Simulation Technology Division, SAIC      then it broke.
  mharrell@std.saic.com