From owner-freebsd-alpha Wed Nov 4 06:31:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA02160 for freebsd-alpha-outgoing; Wed, 4 Nov 1998 06:31:19 -0800 (PST) (envelope-from owner-freebsd-alpha@FreeBSD.ORG) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA02131 for ; Wed, 4 Nov 1998 06:31:11 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.8.5/8.8.5) with ESMTP id JAA29186; Wed, 4 Nov 1998 09:31:03 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.1/8.9.1) id JAA11073; Wed, 4 Nov 1998 09:31:03 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 4 Nov 1998 09:31:02 -0500 (EST) To: Doug Rabson Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: What do these mean? In-Reply-To: References: X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13888.25355.591294.275579@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Doug Rabson writes: > On Tue, 3 Nov 1998, Simon Shapiro wrote: > > > Please save me the source hunting. what do the following messages mean? > > The machine is connected to a 3Com Linkbuilder 9at 100MHz). Everything else > > on that hub is FreeBSD but on the Intel boards, excpet the other Alpha > > which has a built-in tulip. > > > > de0: abnormal interrupt: transmit underflow (raising TX threshold to 96|256) > > de0: abnormal interrupt: transmit underflow (raising TX threshold to > > 128|512) > > de0: abnormal interrupt: transmit underflow (raising TX threshold to > > 160|1024) > > I get these all the time. They are harmless but annoying. The driver > seems to set up the wrong values for one of my de cards and then realise > its mistake later when it gets a few underflows. I had this with NetBSD > too so I haven't tried to debug it. I see this on pretty much every 2114x nic I have in i386 & alpha boxes, running FreeBSD, NetBSD & Digital UNIX. I seem remember looking at the driver a few months ago & concluding that this was proper behaviour. It tends to happen frequently when you make the PCI bus really busy. We see it all the time when using disk arrays & Myrinet. FWIW, Digital UNIX behaves the same way given similar workloads: tu0: transmit FIFO underflow: threshold raised to: 256 bytes tu0: transmit FIFO underflow: threshold raised to: 512 bytes tu0: transmit FIFO underflow: threshold raised to: 1024 bytes tu0: transmit FIFO underflow: using store-forward Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message