From owner-freebsd-hardware Fri Feb 16 7:52:58 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from engr.orst.edu (ENGR.ORST.EDU [128.193.54.1]) by hub.freebsd.org (Postfix) with ESMTP id B99A537B401 for ; Fri, 16 Feb 2001 07:52:55 -0800 (PST) Received: from eel.ENGR.ORST.EDU (eel.ENGR.ORST.EDU [128.193.55.69]) by engr.orst.edu (8.9.3/8.9.3) with ESMTP id HAA18708; Fri, 16 Feb 2001 07:52:54 -0800 (PST) Received: (from shepard@localhost) by eel.ENGR.ORST.EDU (8.9.3/8.9.3) id HAA17329; Fri, 16 Feb 2001 07:52:54 -0800 (PST) Date: Fri, 16 Feb 2001 07:52:54 -0800 From: Darren Shepard To: "Eric A. Sproul" Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: mysterious lock-ups Message-ID: <20010216075254.A17121@eel.ENGR.ORST.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hi, > I am experiencing mysterious lock-ups on a brand new 4.2 box that I > recently built. I have very little evidence to go on since *nothing* is > logged-- making me think it's hardware-related. The system becomes > completely unresponsive from the network as well as the serial > console. All I have that is somewhat unusual are some console messages > related to the net card. > > This system has an FIC AZ-11 board with an AMD Duron 700 and 128 MB of > Kingmax "TinyBGA" SDRAM. I am not overclocking the chip. The hard > drive is a Western Digital WD205BA (20.5 GB 7200 RPM ATA-66). The > network card is a Linksys LNE100TX 10/100 PCI. I have built a custom > kernel with the following netcard support: > > device miibus # MII bus support > device dc # DEC/Intel 21143 and various workalikes > > It shows up in dmesg as: > > > The console messages that I saw were: > > Feb 16 09:13:59 gryphon /kernel: dc0: TX underrun -- increasing TX > threshold > Feb 16 09:14:11 gryphon /kernel: dc0: watchdog timeout > Feb 16 09:56:20 gryphon /kernel: dc0: TX underrun -- increasing TX > threshold > > I have never seen these before so I don't know if they are unusual or > just normal. Could this be related to a lock-up or do I need to check > elsewhere? > > Thanks in advance, > Eric On my 4.2 system with two Linksys LNE100TX cards I frequently recieve similar messages (no 'watchdog timeout', but the 'TX underrun'), usually during times of high network activity. I've been getting these messages for quite some time (IIRC since 4.0), but everything seems to work fine. I'm curious as to their origin though... -- Darren Shepard | dss@orst.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message