From owner-freebsd-questions  Thu Jan 16 14:43:23 2003
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 7A0F537B40E
	for <questions@FreeBSD.ORG>; Thu, 16 Jan 2003 14:43:22 -0800 (PST)
Received: from sage-american.com (adsl-65-71-135-139.dsl.crchtx.swbell.net [65.71.135.139])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6480543E4A
	for <questions@FreeBSD.ORG>; Thu, 16 Jan 2003 14:43:21 -0800 (PST)
	(envelope-from jackstone@sage-one.net)
Received: from sagea (sagea.sage-american [192.168.0.3])
	by sage-american.com (8.12.6/8.12.6) with SMTP id h0GMhGJ7021519;
	Thu, 16 Jan 2003 16:43:16 -0600 (CST)
	(envelope-from jackstone@sage-one.net)
Message-Id: <3.0.5.32.20030116164315.02d84620@mail.sage-one.net>
X-Sender: jackstone@mail.sage-one.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Thu, 16 Jan 2003 16:43:15 -0600
To: Marco Beishuizen <marco@beishuizen.info>,
	FreeBSD questions mailing list <questions@FreeBSD.ORG>
From: "Jack L. Stone" <jackstone@sage-one.net>
Subject: Re: TX underrun
In-Reply-To: <Pine.BSF.4.52.0301162317540.26941@tsunami.bsd>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Status: No, hits=0.0 required=4.5
	tests=IN_REP_TO,SPAM_PHRASE_00_01
	version=2.43-jlsrules1
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-questions.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-questions>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-questions>
X-Loop: FreeBSD.ORG

At 11:22 PM 1.16.2003 +0100, Marco Beishuizen wrote:
>
>Hi,
>
>Recently, I noticed a kernel message on one of my machines:
>
>dc0: TX underrun -- increasing TX threshold
>
>It doesn't seem to be very important. I'm just curious what it means. Does
>anyone know what it means?
>
>Thanks,
>
>Marco
>

This is no problem by itself at the moment, BUT may cause a "crash"
eventually. What you see here is the driver adjusting some buffers to the
network load you have. I have seen this before and it may be okay for now,
but you would be advised to replace with a better NIC. Linksys cards are
commonly known for this issue and apparently is just not able to "shift
gears" well enough. It may be having problems shifting to full duplex.

Best regards,
Jack L. Stone,
Administrator

SageOne Net
http://www.sage-one.net
jackstone@sage-one.net

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message