Major 2.0.27 problems #2 -- an oops for your delight

Chris Evans (chris@ferret.lmh.ox.ac.uk)
Tue, 11 Feb 1997 14:28:16 +0000 (GMT)

After the weekly death of the 3c59x driver, I was removeing then inserting
the module. Shortly after, I was greeted by the following OOPS:

<lots of these>

eth0: Transmitter access conflict.
eth0: Transmitter access conflict.
eth0: Transmitter access conflict.
eth0: vortex_close() status e004, Tx status 88.
3c59x.c:v0.30-all 12/23/96 becker@cesdis.gsfc.nasa.gov
3Com EtherLink III: Overriding PCI latency timer (CFLT) setting of 248, new value is 255.
loading device 'eth0'...
eth0: 3Com 3c590 Vortex 10Mbps at 0x6000, 00:a0:24:6c:18:dc, IRQ 10
Internal config register is 1020010, transceivers 0xe138.
8K byte-wide RAM 1:1 Rx:Tx split, autoselect/10baseT interface.
eth0: Initial media type 10baseT.
eth0: vortex_open() InternalConfig 01020010.
eth0: vortex_open() irq 10 media status 8800.
eth0: Media selection timer tick happened, 10baseT.
eth0: Media 10baseT has link beat, 88c0.
eth0: Media selection timer finished, 10baseT.
invalid operand: 0000
CPU: 0
EIP: 0010:[<00739c12>]
EFLAGS: 00010246
eax: 01d12ee0 ebx: 00000001 ecx: 01d12ee0 edx: 00739c12
esi: 01d12ee0 edi: 00739c98 ebp: 00739c00 esp: 00191214
ds: 0018 es: 0018 fs: 002b gs: 0018 ss: 0018
Process swapper (pid: 0, process nr: 0, stackpage=0018f43c)
Stack: 00138966 01d12ee0 00739c00 01d12ee0 010f760c 01d12830 00739c00 00000000
00000202 001389b2 01d12ee0 00739c00 00000001 001406b7 01d12ee0 00739c00
00000001 01d12ee0 010f760c 00000017 01d12844 00000202 001457e8 010f760c
Call Trace: [<00138966>] [<001389b2>] [<001406b7>] [<001457e8>] [<001440d0>] [<00145127>] [<0013eaa7>]
[<00138b7c>] [<001161e7>] [<0010a52b>] [<001095d4>] [<0010a5a5>] [<001092cc>] [<00109157>] [<00115980>]
[<0011025c>]
Code: ff ff ff ff ff ff 00 00 e8 ca 04 ad 00 63 e0 e0 03 ff ff 00
Aiee, killing interrupt handler
kfree of non-kmalloced memory: 00191484, next= 00000001, order=9017
kfree of non-kmalloced memory: 00191474, next= 00000001, order=9017
kfree of non-kmalloced memory: 00191988, next= 00000001, order=9017
idle task may not sleep
idle task may not sleep
idle task may not sleep
idle task may not sleep
idle task may not sleep

The EIP is out of range.

Call trace goes something like this:

do_dev_queue_xmit
dev_queue_xmit
ip_queue_xmit
tcp_write_xmit
tcp_ack
tcp_rcv
ip_rcv
net_bh
do_bottom_half
system_call
sys_idle
system_call
init
start_kernel
it_real_fn
schedule

Does that sound like a sane trace???

Note that despite claiming "killing interrupt handler", the machine is
still running. It has 8 users hammering away at it at the moment...

Please cc: replies to me.

Cheers,
Chris