From owner-freebsd-hackers Wed Dec 30 09:05:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA05310 for freebsd-hackers-outgoing; Wed, 30 Dec 1998 09:05:13 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rs5s2.datacenter.cha.cantv.net (rs5s2.datacenter.cha.cantv.net [200.44.32.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA05303 for ; Wed, 30 Dec 1998 09:05:11 -0800 (PST) (envelope-from lem@cantv.net) Received: from lg (tc2r9-224.ras.cha.cantv.net [200.44.8.224]) by rs5s2.datacenter.cha.cantv.net (8.9.1a/8.9.1/1.0) with SMTP id NAA29483; Wed, 30 Dec 1998 13:04:37 -0400 (VET) Message-Id: <3.0.6.32.19981230121001.0088e6e0@pop.cantv.net> X-Sender: lem@pop.cantv.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Wed, 30 Dec 1998 12:10:01 -0400 To: Daniel Eischen , mrcpu@internetcds.com, wilko@yedi.iaf.nl From: Luis Munoz Subject: Re: comments on de driver error message? Cc: FreeBSD-hackers@FreeBSD.ORG, eischen@vigrid.com In-Reply-To: <199812300430.XAA10206@pcnet1.pcnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FWIW, I had the same configuration (with switches instead of hubs) and were getting the same errors in a couple of boxes. When I certified the patch cords of the top two machines appearing in the logs with a WireScope 155 I found one of them bad. After replacing both of them, I've seen no more messages like those. At first I was bitching about the cheap cards or the driver but hey, it was the cable. What stroke me is that even with an expensive cable-testing device one of the cables was 'good'! Regards. -lem At 11:30 PM 29/12/98 -0500, Daniel Eischen wrote: >> I tested all mine with a Fluke Lanmeter 6802 to 100mbit, and they all >> checked fine. Only the de0 card reports any errors, nothing else >> (including the hubs and the lan tester) think anything is wrong at all... > >Does the Lanmeter also validate the CRCs in the packets? > >If the de error messages always indicate teh same Ethernet >address(es) and there are other systems in the network that >don't evoke these same messages, then it is hard to point >the finger at the de card. > >In my case, the error message always indicated the same >Ethernet address. It turned out the RJ58 connector was >crimped too hard, so that the metal contacts were recessed >too much and didn't make a good connection when it was >plugged in. The fault was mine because I made the [bad] >cables in the first place :( > >Dan Eischen >eischen@vigrid.com > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message