From owner-freebsd-stable@FreeBSD.ORG Mon Jan 24 09:51:02 2005 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 35B2016A4CE; Mon, 24 Jan 2005 09:51:02 +0000 (GMT) Received: from smtp-vbr8.xs4all.nl (smtp-vbr8.xs4all.nl [194.109.24.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 93B2F43D62; Mon, 24 Jan 2005 09:50:59 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp-vbr8.xs4all.nl (8.12.11/8.12.11) with ESMTP id j0O9ouqK050837; Mon, 24 Jan 2005 10:50:57 +0100 (CET) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.13.1/8.12.9) with ESMTP id j0O9ot4n040179; Mon, 24 Jan 2005 10:50:55 +0100 (CET) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.13.1/8.13.1/Submit) id j0O9otKa040178; Mon, 24 Jan 2005 10:50:55 +0100 (CET) (envelope-from wb) Date: Mon, 24 Jan 2005 10:50:55 +0100 From: Wilko Bulte To: Peter Jeremy Message-ID: <20050124095055.GC40050@freebie.xs4all.nl> References: <20050123135753.14384@mail.net-virtual.com> <20050123232738.GA78226@StefanEsser.FreeBSD.org> <20050124001425.GD241@cirb503493.alcatel.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20050124001425.GD241@cirb503493.alcatel.com.au> X-OS: FreeBSD 4.11-RC2 User-Agent: Mutt/1.5.6i X-Virus-Scanned: by XS4ALL Virus Scanner cc: freebsd-stable@freebsd.org Subject: Re: NIC card problems.... 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, 24 Jan 2005 09:51:02 -0000 On Mon, Jan 24, 2005 at 11:14:26AM +1100, Peter Jeremy wrote.. > On Mon, 2005-Jan-24 00:27:38 +0100, Stefan Eßer wrote: > >The TX threshold messages issued by the dc driver appear more as an > >indication that the PCI bus is under severe load, than as a hint that > >the dc driver is causing the reboots, IMHO. > > Under Tru64, I've seen Tulip cards report backoff to 1024 byte FIFO and > then switching to store-and-forward. That's about 100µsec latency and > nothing should be holding the PCI bus that long. I am inclined to > believe that something is stuffed in the PCI interface logic in the NIC. According to my Tru64 colleagues not all Tulip chip versions are born equal, some are better than others. I do not have more detail here. -- Wilko Bulte wilko@FreeBSD.org