public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <andrewm@uow.edu.au>
To: Josefine Staff <staff@josefine.ben.tuwien.ac.at>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.2.17] 3c59x and Transmit list error
Date: Thu, 02 Nov 2000 19:28:30 +1100	[thread overview]
Message-ID: <3A0125AE.467B640B@uow.edu.au> (raw)
In-Reply-To: <20001102013305.A17809@josefine.ben.tuwien.ac.at>

Markus Fischer wrote:
> 
> Hello,
> 
>         For some time now we're observing a very bad [tm] network
> problem with our 3Com 3c905B Cyclone card. After booting the
> network works just fine, but after a few days ( ranging from five
> to 10) really hard network problems occur, rendering the network
> accessabilty to zero; only manually restarting the network solves
> this problem (from local, of course).

eth0: Transmit error, Tx status register 82.

This is an "out of window collision", otherwise known
as a "Transmit reclaim error".

It is almost certainly caused by another machine on
your network entering full-duplex mode.  It stomps 
on the 3c905's Tx packets and the collision is
detected too late for the 905 to be able to
retransmit - some of the packet contents have
been discarded from the on-chip FIFO.

Next time it happens, you need to run around the
building and find out who just did something such
as turning their computer on, or mucking around
with dangerous Linux netdriver module parameters.

If this description doesn't match your situation
please let me know and we'll work on it.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      reply	other threads:[~2000-11-02  8:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-02  0:33 [2.2.17] 3c59x and Transmit list error Markus Fischer
2000-11-02  8:28 ` Andrew Morton [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3A0125AE.467B640B@uow.edu.au \
    --to=andrewm@uow.edu.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=staff@josefine.ben.tuwien.ac.at \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox