On Sun, 28 May 2000, Tomasz Motylewski wrote:
> I have reported that 3c509.c driver stops receiving interrupts ocasionally
> (once a few days) on all 2.2.13..16 kernels (dual P200).
> I did not have this problem with 2.0.3x kernels.
>
> Recently I have booted 2.2.16pre3 kernel with noapic option.
> Then this problem is much more frequent, about few times per hour when I use
> the machine (remote X11 session) / few times per day when I do not use it.
> ifconfig down/up makes it working again
>
> I am getting messages like:
> eth0: transmit timed out, Tx_status 00 status 2019 Tx FIFO room 3068.
> eth0: transmit timed out, Tx_status 00 status 2019 Tx FIFO room 3068.
Yup, the hardware is raising the interrupt.
The driver is waiting for the interrupt handler to be run.
But the handler has stopped being run.
BTW, the 3c509 support web page is at
http://scyld.com/network/3c509.html
But that page will only tell you that an interrupt is being raised.
> eth0 Link encap:Ethernet HWaddr 00:60:97:5C:D6:71
> RX packets:981582 errors:0 dropped:0 overruns:0 frame:0
> TX packets:78515 errors:4 dropped:0 overruns:0 carrier:1
> collisions:461 txqueuelen:100
> Interrupt:10 Base address:0x300
You were running for quite a while before the problem showed up.
> lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:3924 Metric:1
> RX packets:506 errors:0 dropped:0 overruns:0 frame:0
> TX packets:506 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
[[ Two 'cat /proc/interrupts' ]]
> 10: 982790 0 XT-PIC eth0
..
> 10: 982790 0 XT-PIC eth0
Presumably no more interrupts are being counted.
Yup, it looks like an interrupt dispatch problem, not a 3c509 driver problem.
Donald Becker [EMAIL PROTECTED]
Scyld Computing Corporation http://www.scyld.com
410 Severn Ave. Suite 210 Annapolis MD 21403
-
Linux SMP list: FIRST see FAQ at http://www.irisa.fr/prive/dmentre/smp-howto/
To Unsubscribe: send "unsubscribe linux-smp" to [EMAIL PROTECTED]
