...[recent 2.4-based kernel]...
> but this problem is not specific to that kernel. I've been having
> it for a looong time.
>
> Specifically, I get:
>
> NETDEV WATCHDOG: eth0: transmit timed out
...
> and then the machine is dead, network-wise. I have to reboot (reset).
>
> Note that I am on an ABIT BP6 board, and I do get a lot of APIC errors
> under heavy network traffic, which is what raises the above.
> By heavy network traffic, I mean a 7 Mb/s full duplex (it's a 100 Mb/s
> LAN).
I had what looks like exactly this problem with my ABIT BP6 -based machine
running RH 7.1, and the problem turned out to be the interaction between
SMP and the APM BIOS, when APM is turned on. A different network card,
but the same symptom. Another symptom I would occasionally see was a
certain kind of hard-disk hang, but only on the integrated HPT366
controller.
I suggest you try either:
-- adding the "noapic" line to your kernel command-line (which will
lose you some I/O performance since normal interrupts will not be
handled APIC-style)
-- completely disabling APM from your kernel configuration. Using
"apm=off/disabled" (I can't remember the exact one you're supposed
to use here) does not totally disable APM usage.
This brings me to my other point. During the Linux kernel startup
code (in the early assembly), the APM BIOS checking code leaves the
BIOS in the "connected" state even if the kernel option for disabling
APM or the SMP forced disable of APM is triggered.
This makes various motherboards (such as the ABIT BP6) unstable.
The Right Thing to do would be to disconnect the APM BIOS if it is
determined that APM support should be disabled.
I could probably generate a patch to fix this if it looked like it would
be accepted by the folks maintaining APM support...
--
Erich Stefan Boleyn <erich@uruk.org> http://www.uruk.org/
"Reality is truly stranger than fiction; Probably why fiction is so popular"
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/