Messages in this thread | | | Date | Mon, 27 Oct 2003 11:18:27 -0800 | From | Andrew Morton <> | Subject | Re: Transmit timeout with 3c395, 2.4.19, 2.4.22 |
| |
Norbert Preining <preining@logic.at> wrote: > > Hi Andrew, hi list! > > Suddenly, after 160 days of running, our bridged firewall started to > spit out this: > NETDEV WATCHDOG: eth1: transmit timed out > > ... > > This always happened with eth1, so we think it *may* a hardware error > creeping in. I would like to know wether this can be the case, or > wether there is something else (switches on the other side, ...) which > may have produced these errors.
Yes, a bad cable might explain this. Or another host which is babbling away all the time (on a half-duplex setup).
- 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/
| |