Messages in this thread | | | Date | Thu, 24 Jan 2002 00:49:57 +0100 (CET) | From | Urban Widmark <> | Subject | Re: via-rhine timeouts |
| |
On Wed, 23 Jan 2002, Justin A wrote:
> I don't think thats the full problem, I just noticed I had been getting > errors too with the via driver, but it's been working fine otherwise: > [snip] > Jan 23 09:45:52 bouncybouncy kernel: eth0: Transmit error, Tx status 8100. > Jan 23 09:49:33 bouncybouncy kernel: eth0: Transmit error, Tx status 8100. > Jan 23 09:51:50 bouncybouncy kernel: eth0: Transmit error, Tx status 8100. > Jan 23 17:55:15 bouncybouncy kernel: eth0: Transmit error, Tx status 8100.
0100 is that it sees too many collisions. The netdev watchdog I can trigger seems to be caused by a lot of collisions.
> Is it possible that the problem is with the hub and via-rhine resetting > the card repetedly just makes it worse?
The hub can be the problem and I suppose resetting could make something worse (if it is done wrong, for example).
/Urban
- 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/
| |