lkml.org 
[lkml]   [1998]   [Jul]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 2.0.34 and 3c595: transmit error, tx status register ..
On Mon, 20 Jul 1998, tilo winkler wrote:

> Hi,
>
> I had been using 2.0.33 without problems for a long time. I had to
> upgrade to 2.0.34 because of the bugs in the tcp/ip code which caused my
> machine to crash. Anyway, since the upgrade to 2.0.34 I have the
> following messages in my syslog sporadically. Its not only that they get
> logged, the machine is also sometimes not available via network, but
> this also recovers after a minute or so.
>
> Jul 20 17:59:34 snafu kernel: eth0: Transmit error, Tx status register
> 90.

This almost always has to be a bad cable/transceiver/termination, etc.
If you use thin-wire, this usually is caused by the shield becoming
separated at a crimp-on connector.

Basically, there isn't much that software can do to cause a transmit
error because the controllers will even transmit junk if told to do
so.

Cheers,
Dick Johnson
***** FILE SYSTEM MODIFIED *****
Penguin : Linux version 2.1.108 on an i586 machine (66.15 BogoMips).
Warning : It's hard to remain at the trailing edge of technology.


-
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.altern.org/andrebalsa/doc/lkml-faq.html

\
 
 \ /
  Last update: 2005-03-22 13:43    [W:0.054 / U:3.896 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site