From owner-freebsd-stable Fri Jul 28 1:49:49 2000 Delivered-To: freebsd-stable@freebsd.org Received: from fingers.noc.uunet.co.za (fingers.noc.uunet.co.za [196.31.1.59]) by hub.freebsd.org (Postfix) with ESMTP id C062D37C29F for ; Fri, 28 Jul 2000 01:49:43 -0700 (PDT) (envelope-from robh@fingers.noc.uunet.co.za) Received: from robh (helo=localhost) by fingers.noc.uunet.co.za with local-smtp (Exim 3.13 #1) id 13I5pp-0009ml-00 for freebsd-stable@freebsd.org; Fri, 28 Jul 2000 10:49:37 +0200 Date: Fri, 28 Jul 2000 10:49:35 +0200 (SAST) From: fingers X-Sender: robh@fingers.noc.uunet.co.za To: freebsd-stable@freebsd.org Subject: tx transmission errors with xl Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I saw a few months ago that if I got errors like these: Jul 28 10:41:15 fingers /kernel: xl1: tx underrun, increasing tx start threshold to 600 bytes Jul 28 10:41:15 fingers /kernel: xl1: tx underrun, increasing tx start threshold to 600 bytes I could increase: #define XL_MIN_FRAMELEN 300 in if_xlreg.h and rebuild kernel. I would have thought that this would have been fixed by now? Upping it to 300 seemed to be sufficient, but I've now had to up it to 600. My question is, is this a "tweak" that I need to do every time after I rebuild my kernel, or is this a problem with the driver? I've searched the archives at www.freebsd.org/search and have found many posts in the lists about this, but no definitive answer. Some blamed it on a cable, some suggested a device hogging the bus etc. Regards --Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message