> kernel: eth0: reset did not complete in 10 ms.
> kernel: NETDEV WATCHDOG: eth0: transmit timed out
> kernel: eth0: Transmit timed out, status 0000, PHY status 782d,
> resetting...
>
> Removing the ethernet cable, unloading/loading the module doesn't change a
> thing, only a cold reboot fixes the problem (until next time).
>
> Is this a known problem? Any fixes?
The effect (the timeout) can be caused by lots of things. Here it sounds
like the chip has locked up (more or less) since you need a cold boot to
recover. Why? Well ...
"Ivan G" has posted recently on via-rhine problems. For him it is only
that the driver stalls but not the need for a full reboot (IIRC).
Simple things you could try is to test some other variants of the driver:
+ Donald Becker's original
http://www.scyld.com/network/via-rhine.html
+ VIAs modified version
http://www.viaarena.com/?PageID=71#lan
If either works better then the next step would be to find out why (and
copy those bits).
The diff between the VIA version and the other is large. I started looking
at merging what they have done to the in-kernel driver.
/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/