From owner-freebsd-hackers Fri Jan 17 08:54:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA13697 for hackers-outgoing; Fri, 17 Jan 1997 08:54:21 -0800 (PST) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id IAA13689 for ; Fri, 17 Jan 1997 08:54:17 -0800 (PST) Received: by iafnl.es.iaf.nl with UUCP id AA22807 (5.67b/IDA-1.5 for freebsd-hackers@freefall.freebsd.org); Fri, 17 Jan 1997 17:53:46 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.7.5/8.6.12) id VAA01928; Thu, 16 Jan 1997 21:46:19 +0100 (MET) From: Wilko Bulte Message-Id: <199701162046.VAA01928@yedi.iaf.nl> Subject: Re: le0 - excessive collisions To: kuku@gilberto.physik.rwth-aachen.de Date: Thu, 16 Jan 1997 21:46:19 +0100 (MET) Cc: freebsd-hackers@freefall.freebsd.org In-Reply-To: <199701161804.TAA01613@gilberto.physik.rwth-aachen.de> from "Christoph Kukulies" at Jan 16, 97 07:04:18 pm X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Christoph Kukulies wrote... > > and replaced it - after I got stumped with two no more functioning > > SMC Ultra 8216 - by a DE200 (le0). > > > > I'm seeing a bunch of > > le0: lance: warning: excessive collisions: TDR 5600ns (554-655m) > > le0: lance: warning: excessive collisions: TDR 5600ns (554-655m) > > le0: lance: warning: excessive collisions: TDR 5500ns (544-643m) > > le0: lance: warning: excessive collisions: TDR 5500ns (544-643m) > > le0: > > > > in my /var/log/messages. > > > > device le0 at isa? port 0x200 net irq 10 iomem 0xd0000 vector le_intr I've observed the same phenomenon on my DE422 (EISA) equipped 486DX22 at work. It means the card sees either a lot of collisions or the cable/terminator itself is interrupted. On my machine I even saw (when the network was *very* congested) the DE422 turn completely deaf. An ifconfig down/up solves this. A surplus ethernet bridge that I used to 'bridge' my own little piece of the network from the evil colliding outside world solved this 8-) So much for a hardware fix for something that looks like a driver problem.. (I know, I should try to find out why this happens) Wilko _ ____________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl - Arnhem, The Netherlands |/|/ / / /( (_) Do, or do not. There is no 'try' - Yoda --------------------------------------------------------------------------