linux-kernel - Re: 3c905B - Transmit error, Tx status register 82

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <75b66ecd0703011013h704319c4h9f5ad7b572c53b28@mail.gmail.com>
Date:	Thu, 1 Mar 2007 13:13:32 -0500
From:	"Lee Revell" <rlrevell@...-job.com>
To:	"WHITE, JOE (ASI-AIT)" <jw2365@....com>
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/