Liam Helmer wrote:
>
> [ tx timeouts with 3x59x and eepro100 ]
>
> ---
>
> Apr 24 15:47:49 colo-firewall kernel: NETDEV WATCHDOG: eth0: transmit
> timed out Apr 24 15:47:49 colo-firewall kernel: eth0: transmit timed out,
> tx_status 00 status e601. Apr 24 15:47:49 colo-firewall kernel:
> diagnostics: net 0cfa media 8880 dma 0000003a. Apr 24 15:47:49
> colo-firewall kernel: eth0: Interrupt posted but not delivered -- IRQ
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This is probably the APIC bug. Are you running SMP? Are
you running UP with the IO-APIC option?
Fixes for this include:
1: Boot SMP with the `noapic' option.
2: Don't configure your UP kernel to use IO-APIC
3: Use 2.4.x-ac kernels, which have a workaround.
> -----
>
> May 4 12:52:28 colo-firewall kernel: NETDEV WATCHDOG: eth2: transmit
> timed out May 4 12:52:28 colo-firewall kernel: eth2: Transmit timed out:
> status f048 0c00 at 517424/517452 command 200ca000. May 4 12:54:12
> colo-firewall kernel: NETDEV WATCHDOG: eth2: transmit timed out May 4
> 12:54:12 colo-firewall kernel: eth2: Transmit timed out: status f048 0c00
> at 517452/517480 command 0001a000. May 4 12:55:00 colo-firewall kernel:
> NETDEV WATCHDOG: eth2: transmit timed out May 4 12:55:00 colo-firewall
> kernel: eth2: Transmit timed out: status f048 0c00 at 517480/517508
> command 0001a000.
> May 4 12:57:40 colo-firewall kernel: NETDEV WATCHDOG: eth2: transmit
> timed out
This will be the same thing. The eepro100 is sharing the
interrupt with the 3com NIC. The 3com NIC does a disable_irq()
while the eepro100 is generating an interrupt and the APIC
falls over.
Rumour has it that the APIC fix will be sent into Linus RSN.
Until then, use `noapic'.
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
