[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0D69EE79F863484FB73D20A95656730D02F9CBB3@ILNORT1MSGUSR18.ITServices.sbc.com>
Date: Thu, 1 Mar 2007 16:08:24 -0600
From: "WHITE, JOE \(ASI-AIT\)" <jw2365@....com>
To: "Lee Revell" <rlrevell@...-job.com>
Cc: <andrewm@....edu.au>, <netdev@....sgi.com>,
<linux-kernel@...r.kernel.org>
Subject: RE: 3c905B - Transmit error, Tx status register 82
Lee,
Thanks for the reply.
We have tried moving my network connection to a new switch, replaced the
cables, but still getting that error.
What do I do with that command options 3c59x full_duplex=1, where do I
put it? Bare with me as I am a newbie.
Thanks,
Joe
-----Original Message-----
From: rlrevell@...il.com [mailto:rlrevell@...il.com] On Behalf Of Lee
Revell
Sent: Thursday, March 01, 2007 12:14 PM
To: WHITE, JOE (ASI-AIT)
Cc: andrewm@....edu.au; netdev@....sgi.com; linux-kernel@...r.kernel.org
Subject: Re: 3c905B - Transmit error, Tx status register 82
On 3/1/07, WHITE, JOE (ASI-AIT) <jw2365@....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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists