mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Lee Revell" <rlrevell@joe-job.com>
To: "WHITE, JOE (ASI-AIT)" <jw2365@att.com>
Cc: andrewm@uow.edu.au, netdev@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: 3c905B - Transmit error, Tx status register 82
Date: Thu, 1 Mar 2007 13:13:32 -0500	[thread overview]
Message-ID: <75b66ecd0703011013h704319c4h9f5ad7b572c53b28@mail.gmail.com> (raw)
In-Reply-To: <0D69EE79F863484FB73D20A95656730D02F9CBA1@ILNORT1MSGUSR18.ITServices.sbc.com>

On 3/1/07, WHITE, JOE (ASI-AIT) <jw2365@att.com> wrote:
> Mar  1 09:44:04 thor kernel: Probably a duplex mismatch.  See
> Documentation/networking/vortex.txt

Um... did you check Documentation/networking/vortex.txt?

261	Transmit error, Tx status register 82
262	-------------------------------------
263	
264	This is a common error which is almost always caused by another host on
265	the same network being in full-duplex mode, while this host is in
266	half-duplex mode.  You need to find that other host and make it run in
267	half-duplex mode or fix this host to run in full-duplex mode.
268	
269	As a last resort, you can force the 3c59x driver into full-duplex mode
270	with
271	
272		options 3c59x full_duplex=1
273	
274	but this has to be viewed as a workaround for broken network gear and
275	should only really be used for equipment which cannot autonegotiate.
276	

Lee

  reply	other threads:[~2007-03-01 18:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-01 16:25 WHITE, JOE (ASI-AIT)
2007-03-01 18:13 ` Lee Revell [this message]
2007-03-01 22:08   ` WHITE, JOE (ASI-AIT)
2007-03-01 22:15     ` Lee Revell

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=75b66ecd0703011013h704319c4h9f5ad7b572c53b28@mail.gmail.com \
    --to=rlrevell@joe-job.com \
    --cc=andrewm@uow.edu.au \
    --cc=jw2365@att.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    /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®