From owner-freebsd-net Tue Feb 26 5: 0: 3 2002 Delivered-To: freebsd-net@freebsd.org Received: from ns1.hexanet.fr (ns1.hexanet.fr [194.98.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 9D35437B400 for ; Tue, 26 Feb 2002 04:59:57 -0800 (PST) Received: from snowflake (olrick@snowflake.hexanet.fr [194.98.140.144]) by ns1.hexanet.fr (8.9.3/8.9.3) with SMTP id NAA62407 for ; Tue, 26 Feb 2002 13:59:56 +0100 (CET) (envelope-from y.grossel@hexanet.fr) Date: Tue, 26 Feb 2002 13:59:57 +0100 From: Yann GROSSEL To: freebsd-net@FreeBSD.ORG Subject: dc TX underrun message, again Message-Id: <20020226135957.76d64546.y.grossel@hexanet.fr> Organization: Hexanet X-Mailer: Sylpheed version 0.7.2 (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, Thanks to all people who have answered me about my previous mail (yesterday) about "TX underrun" messages. Today we put this firewall box in production mode. Almost immediately, new messages have been logged (as expected) : Feb 26 13:03:15 blade /kernel: dc2: TX underrun -- increasing TX threshold Feb 26 13:03:18 blade /kernel: dc2: TX underrun -- increasing TX threshold Feb 26 13:03:31 blade /kernel: dc2: TX underrun -- increasing TX threshold Feb 26 13:04:23 blade /kernel: dc3: TX underrun -- increasing TX threshold Feb 26 13:04:23 blade /kernel: dc3: TX underrun -- increasing TX threshold Feb 26 13:05:40 blade /kernel: dc3: TX underrun -- increasing TX threshold But after a few minutes of activity : Feb 26 13:19:22 blade /kernel: dc3: TX underrun -- using store and forward mode Feb 26 13:24:33 blade /kernel: dc2: TX underrun -- using store and forward mode Are these new messages indicating a more serious problem ? Or is it harmless to ignore them ? Thanks for any answers Yann To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message