Messages in this thread | | | Date | Wed, 28 Jul 1999 19:12:26 +0200 | From | Matthew Wilcox <> | Subject | Re: 2.2.10 & EtherExpress 16 "CU wedged, status 0040 0000" |
| |
On Wed, Jul 28, 1999 at 09:17:57AM -0300, Ben Armstrong wrote: > Jul 27 00:53:11 sanctuary kernel: eth0: CU wedged, status 0040 0000, resetting... > Jul 27 00:53:11 sanctuary kernel: eth0: i82586 reset timed out, kicking... > Jul 27 00:53:11 sanctuary last message repeated 4 times > Jul 27 00:53:11 sanctuary kernel: eth0: i82586 not responding, giving up. > Jul 27 00:53:21 sanctuary kernel: eth0: transmit timed out, board on fire?
I experienced the same thing under Linux 2.0.29 which was the first and last time I had a machine with this ethernet card in it. It also corrupts data in a way which silently evades all potential checksums at the same time. For example, I ftp'd a linux tarball and it had an error in it for each time this message occurred.
Do yourself a favour; throw this pile of crap in the bin and buy an NE2k clone at a trade fair for $2. You will get better performance.
-- Matthew Wilcox <willy@bofh.ai> "Windows and MacOS are products, contrived by engineers in the service of specific companies. Unix, by contrast, is not so much a product as it is a painstakingly compiled oral history of the hacker subculture." - N Stephenson
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |