mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <andrewm@uow.edu.au>
To: Wilfried Weissmann <Wilfried.Weissmann@gmx.at>
Cc: "Kevin P. Fleming" <kevin@labsysgrp.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.7-pre7 natsemi network driver random pauses
Date: Fri, 20 Jul 2001 02:48:20 +1000	[thread overview]
Message-ID: <3B570F54.D4087993@uow.edu.au> (raw)
In-Reply-To: <00f101c1106e$a119e3c0$6baaa8c0@kevin> <3B570CCD.BC6A16C7@gmx.at>

Wilfried Weissmann wrote:
> 
> Just for curiosity, do you have those messages in our logfiles:
> 
> eth0: Transmit error, Tx status register 82.

That's a 3com message, not natsemi.

And it's such a common error that it is now specially detected in the
driver:

            if (tx_status == 0x82) {
                printk(KERN_ERR "Probably a duplex mismatch.  See "
                        "Documentation/networking/vortex.txt\n");

Which expands to:


Transmit error, Tx status register 82
-------------------------------------

This is a common error which is almost always caused by another host on
the same network being in full-duplex mode, while this host is in
half-duplex mode.  You need to find that other host and make it run in
half-duplex mode or fix this host to run in full-duplex mode.

As a last resort, you can force the 3c59x driver into full-duplex mode
with

        options 3c59x full_duplex=1

but this has to be viewed as a workaround for broken network gear and
should only really be used for equipment which cannot autonegotiate.

-

      reply	other threads:[~2001-07-19 16:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-19 16:19 Kevin P. Fleming
2001-07-19 16:37 ` Wilfried Weissmann
2001-07-19 16:48   ` 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=3B570F54.D4087993@uow.edu.au \
    --to=andrewm@uow.edu.au \
    --cc=Wilfried.Weissmann@gmx.at \
    --cc=kevin@labsysgrp.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®