From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 02:58:52 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D8C8916A4CE for ; Mon, 12 Jan 2004 02:58:52 -0800 (PST) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id 7B4A843D2D for ; Mon, 12 Jan 2004 02:58:50 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 12 Jan 2004 10:58:49 +0000 (GMT) To: Brandon Fosdick In-reply-to: Your message of "Sun, 11 Jan 2004 16:22:17 PST." <4001E8B9.6070407@terrandev.com> X-Request-Do: Date: Mon, 12 Jan 2004 10:58:48 +0000 From: David Malone Message-ID: <200401121058.aa41556@salmon.maths.tcd.ie> cc: David Malone cc: "Shawn K. Quinn" cc: stable@freebsd.org Subject: Re: Very weird problem with dc driver X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2004 10:58:53 -0000 > >>Dec 25 00:32:58 xevious /kernel: dc0: TX underrun -- increasing TX > >>threshold > > In general, you don't need to worry about these, they are just the driver > > adjusting itself to the speed of your card/motherboard. You may see a few > > of them when the machine is first busy after boot, and then they should > > probably stop. > I have a machine running 4.9 and using the dc driver (Netgear FA310TX) > that gets lots of these messages. For the most part they happen when the > network cable is unplugged, but I also get a number of them randomly. > They're not entirely harmless either since the umass driver seems to be > affected. If one of the messages pops up while transferring to/from a > usb drive the transfer stalls in poll (according to top) and any > subsequent attempt to access (ls,cd, etc) either disk involved in the > transfer also gets locked in the poll state. While it's possible that the TX underrun is somehow causing your USB subsystem to stall, it seems more likely that either the USB subsystem is stalling your NIC or that something else is stalling both of them. > Google found a few other threads but I don't feel like listing them. Most of the threads that you posted say roughly what I's said, "don't worry about them". One did mention that there may be hardware problems with the Netgear card that you mention. However, the section of the driver man page quoted suggests that the driver contains work-arounds for these problems. David.