Transmit timed out/transmit timer stopped! message and hang with Linksys LNE100TX and 0.90f
Jason Thomas
jason@topic.com.au
Sun Apr 9 20:20:36 2000
--gKMricLos+KVdGMg
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
i had the same problem a while back with and older tulip.c upgrading got rid
of the problem, alot of other people have experienced this same thing as
well...
Steve Bergman [steve@uhura.netplus.net] wrote:
> Hi,
>
> I have spent the weekend fighting Linksys cards. I was getting frequent
> hangs with my older Linksys liteon xxxxxx169 based cards (using various
> drivers from 0.89H to 0.91x) and finally went out and got new Linksys
> LNE100TX WOL cards and installed the linksys provided 0.90f driver from
> diskette 2. I am connected through a linksys 5 port hub. Everything
> looked great. I was torure testing using the following schedule:
>
> ~45% of time ftp'ing from machine A to B and B to A simultaneously
> ~22% of time ftp'ing from machine A to B
> ~22% of time ftp'ing from machine B to A
> ~11% of time idle
>
> (Files were 1GB in size)
>
> Everything looked great. Sum of sent and received packets ~ 46,000,000
>
> After 3 or 4 hours, started getting messages of the form:
>
> Apr 9 16:56:18 voyager kernel: eth0: Transmit timed out, status
> ec660000, CSR12 40a1d0cc, resetting...
> Apr 9 16:56:18 voyager kernel: eth0: The transmitter stopped! CSR5 is
> ec678006, CSR6 1a82202.
> Apr 9 16:56:23 voyager kernel: eth0: Transmit timed out, status
> e4660000, CSR12 40a1d0cc, resetting...
> Apr 9 16:56:23 voyager kernel: eth0: The transmitter stopped! CSR5 is
> e4678006, CSR6 1a82202.
> Apr 9 16:56:28 voyager kernel: eth0: Transmit timed out, status
> e4660000, CSR12 40a1d0cc, resetting...
> Apr 9 16:56:28 voyager kernel: eth0: The transmitter stopped! CSR5 is
> e4678006, CSR6 1a82202.
> Apr 9 16:56:33 voyager kernel: eth0: Transmit timed out, status
> e4660000, CSR12 40a1d0cc, resetting...
> Apr 9 16:56:33 voyager kernel: eth0: The transmitter stopped! CSR5 is
> e4678006, CSR6 1a82202.
> Apr 9 16:56:38 voyager kernel: eth0: Transmit timed out, status
> e4660000, CSR12 40a1d0cc, resetting...
> Apr 9 16:56:38 voyager kernel: eth0: The transmitter stopped! CSR5 is
> e4678006, CSR6 1a82202.
> Apr 9 16:56:43 voyager kernel: eth0: Transmit timed out, status
> e4660000, CSR12 40a1d0cc, resetting...
> Apr 9 16:56:43 voyager kernel: eth0: The transmitter stopped! CSR5 is
> e4678006, CSR6 1a82202.
> Apr 9 16:56:48 voyager kernel: eth0: Transmit timed out, status
> e4660000, CSR12 40a1d0cc, resetting...
> Apr 9 16:56:48 voyager kernel: eth0: The transmitter stopped! CSR5 is
> e4678006, CSR6 1a82202.
> Apr 9 16:56:53 voyager kernel: eth0: Transmit timed out, status
> e4660000, CSR12 40a1d0cc, resetting...
> Apr 9 16:56:53 voyager kernel: eth0: The transmitter stopped! CSR5 is
> e4678006, CSR6 1a82202.
> Apr 9 16:56:58 voyager kernel: eth0: Transmit timed out, status
> e4660000, CSR12 40a1d0cc, resetting...
> Apr 9 16:56:58 voyager kernel: eth0: The transmitter stopped! CSR5 is
> e4678006, CSR6 1a82202.
> Apr 9 16:57:03 voyager kernel: eth0: Transmit timed out, status
> e4660000, CSR12 40a1d0cc, resetting...
> Apr 9 16:57:03 voyager kernel: eth0: The transmitter stopped! CSR5 is
> e4678006, CSR6 1a82202.
>
> on one of the machines during a period in which they were both
> sending/receiving at the same time.
>
> "ifconfig eth0 down;ifconfig eth0 up" on the machine giving the
> messages got things going again.
>
> (Debug level was a the default for the driver and the driver was
> compiled as a module.)
>
> Any help would be greatly appreciated. I have tried a few different
> cards and encountered problems that are potentially embarrassing for me
> and (more importantly) Linux if they were to occur at work on a live
> machine. I am looking for a card/driver combination that is:
>
> 1. Reliable!!!!!!!!
> 2. A good performer
> 3. Inexpensive
>
> The tulip based cards look really promising to me but I *must* be
> confident of the reliability.
>
> Please let me know if there is any specific testing I can do.
>
> On another note, is it considered poor form to post this to both
> linux-tulip and linux-tulip-bug?
>
> Thanks,
> Steve Bergman
>
> P.S. As always, Thank You to Donald and others who have made this
> problem possible. ;-)
>
>
>
> -------------------------------------------------------------------
> To unsubscribe send a message body containing "unsubscribe"
> to linux-tulip-request@beowulf.org
--
Jason Thomas Phone: +61 2 6257 7111
System Administrator - UID 0 Fax: +61 2 6257 7311
tSA Consulting Group Pty. Ltd. Mobile: 0418 29 66 81
1 Hall Street Lyneham ACT 2602 http://www.topic.com.au/
--gKMricLos+KVdGMg
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 5.0i for non-commercial use
MessageID: 6zu949m+Qy4TJHEGN4I01FYG4yBo0Jvk
Comment: Ha Ha
iQA/AwUBOPEeS+3GMESSUoi+EQJLkgCg/hFG1bxILhV1fBt4cvSJ/KEacAIAnRq9
2yuxPccVwAqQYtRlYpCvdD6q
=A/aw
-----END PGP SIGNATURE-----
--gKMricLos+KVdGMg--
-------------------------------------------------------------------
To unsubscribe send a message body containing "unsubscribe"
to linux-tulip-bug-request@beowulf.org