From owner-freebsd-questions Wed Nov 21 15: 7:53 2001 Delivered-To: freebsd-questions@freebsd.org Received: from mta02-svc.ntlworld.com (mta02-svc.ntlworld.com [62.253.162.42]) by hub.freebsd.org (Postfix) with ESMTP id 8C27737B416 for ; Wed, 21 Nov 2001 15:07:47 -0800 (PST) Received: from lungfish.ntlworld.com ([62.253.144.198]) by mta02-svc.ntlworld.com (InterMail vM.4.01.03.13 201-229-121-113) with ESMTP id <20011121230745.MPJF14383.mta02-svc.ntlworld.com@lungfish.ntlworld.com>; Wed, 21 Nov 2001 23:07:45 +0000 Received: from boog.goatsucker.org (boog.goatsucker.org [192.168.1.3]) by lungfish.ntlworld.com (8.11.3/8.11.3) with ESMTP id fALN7Qn05699; Wed, 21 Nov 2001 23:07:26 GMT (envelope-from scott@boog.goatsucker.org) Received: (from scott@localhost) by boog.goatsucker.org (8.9.3/8.9.3) id XAA05174; Wed, 21 Nov 2001 23:06:55 GMT (envelope-from scott) Date: Wed, 21 Nov 2001 23:06:55 +0000 From: Scott Mitchell To: Anthony Atkielski Cc: FreeBSD Questions Subject: Re: Error on xl0 Message-ID: <20011121230655.B307@localhost> References: <010b01c172d6$186032d0$0a00000a@atkielski.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <010b01c172d6$186032d0$0a00000a@atkielski.com>; from anthony@freebie.atkielski.com on Wed, Nov 21, 2001 at 10:47:18PM +0100 X-Operating-System: FreeBSD 4.1-RELEASE i386 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Nov 21, 2001 at 10:47:18PM +0100, Anthony Atkielski wrote: > What does this error message mean on the console: > > xl0: transmission error: 90 > xl0: tx underrun, increasing tx start threshold to 120 bytes At a guess, it means your Ethernet card ran out of data to send partway through a packet. I imagine it starts transmitting as soon as it has x bytes of a packet rather than waiting for the whole thing, and for some reason the rest of these packets wasn't delivered to it in time. The driver apparently increased the value of x in an attempt to prevent this from happening again. > It occured three times in a row while I was doing make install for fvwm2. A lack of bandwidth somewhere in your system could cause this kind of thing... were you generating a lot of network traffic and hammering your disk(s) at the same time with the fvwm compile? Was the machine otherwise busy somehow? I believe from previous exchanges that you're running a board with a VIA 686 southbridge -- these *are* known to have issues with data corruption and sensitivity wrt what's plugged in where on the PCI bus. http://www.viahardware.com/ has the best FAQ on the subject that I've found. There may be other equally plausible explanations, but I don't think we have sufficient information to make a definitive judgement. HTH, Scott -- =========================================================================== Scott Mitchell | PGP Key ID | "Eagles may soar, but weasels Cambridge, England | 0x54B171B9 | don't get sucked into jet engines" scott.mitchell@mail.com | 0xAA775B8B | -- Anon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message