On Sat, 19 May 2001, Donald Becker wrote:
> > eth1: Transmit timeout, status 0c 0005 media 18.
> > eth1: Tx queue start entry 4 dirty entry 0.
> > eth1: RTL8139 Interrupt line blocked, status 5.
> > eth1: RTL8139 Interrupt line blocked, status 5.
> > eth1: RTL8139 Interrupt line blocked, status 4.
> > eth1: RTL8139 Interrupt line blocked, status 4.
> > (continues every minute with status 4 if no traffic on interface)
>
> The card is reporting that the interrupt line has been asserted (Tx
> done), but the interrupt handler hasn't been called.
>
> You can verify this by watching the interrupt count in /proc/interrupts.
>
> Try booting the kernel with "noapic", which we recommend as the safe
> default setting.
Sorry, this didn't work out. I still get Tx descriptor dumps, and these:
eth1: RTL8139 Interrupt line blocked, status 5.
eth1: Transmit timeout, status 0c 0005 media 18.
eth1: Tx queue start entry 8 dirty entry 4, full.
eth1: Tx descriptor 0 is 9008a03c. (queue head)
eth1: Tx descriptor 1 is 9008a03c.
eth1: Tx descriptor 2 is 9008a03c.
eth1: Tx descriptor 3 is 9008a03c.
eth1: MII #32 registers are: 1000 782d 0000 0000 01e1 0000 0000 0000.
eth1: RTL8139 Interrupt line blocked, status 5.
/proc/interrupt looks like this:
CPU0
0: 37029 XT-PIC timer
1: 1049 XT-PIC keyboard
2: 0 XT-PIC cascade
4: 1955 XT-PIC serial
5: 173 XT-PIC ide2, eth0
8: 1 XT-PIC rtc
9: 0 XT-PIC eth1
10: 1323 XT-PIC serial
11: 41 XT-PIC sym53c8xx, es1371
13: 1 XT-PIC fpu
14: 14947 XT-PIC ide0
NMI: 0
So, yes, it looks as if there had not been a single eth1 IRQ. But why
does 2.4 get it right, then, even without special boot options?
--
Matthias Andree
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
