From owner-freebsd-stable@FreeBSD.ORG Mon Jan 24 00:00:36 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 3351E16A4D4 for ; Mon, 24 Jan 2005 00:00:36 +0000 (GMT) Received: from net-virtual.com (net-virtual.com [69.55.238.186]) by mx1.FreeBSD.org (Postfix) with SMTP id DB92A43D49 for ; Mon, 24 Jan 2005 00:00:35 +0000 (GMT) (envelope-from mailinglists@net-virtual.com) Received: (qmail 82959 invoked by uid 0); 24 Jan 2005 00:00:35 -0000 Received: from unknown (HELO ?192.168.1.100?) (gregs%net-virtual.com@67.169.110.208) by net-virtual.com with SMTP; 24 Jan 2005 00:00:35 -0000 From: "Net Virtual Mailing Lists" To: =?ISO-8859-1?Q?Stefan=20E=DFer?= , Date: Sun, 23 Jan 2005 16:00:32 -0800 Message-Id: <20050124000032.8308@mail.net-virtual.com> In-Reply-To: <20050123232738.GA78226@StefanEsser.FreeBSD.org> References: <20050123232738.GA78226@StefanEsser.FreeBSD.org> X-Mailer: CTM PowerMail 4.2.1 us Carbon MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 00:00:36 -0000 Hello Stefan (and everyone else!), Thank you for your great comments! I think I have a 3c9xx card around here somewhere, I will give that a shot when it reboots the next time (just to see). It looks like for future systems I'll standardize on the Intel fxp-based cards, I really appreciate that advice! As for what might actually be causing this crash: I just checked the PCI configuration and don't see anything in the BIOS which would suggest that anything you mentioned is something I can modify - is that correct? Or are you saying that I am simply pushing past the limits of what this hardware (and PCI bus) is capable of? For whatever it is worth, all I have in terms of PCI cards is this NIC and VGA card (which doesn't run anything gui-like). I am using the onboard IDE controller, not sure if that is considered a "PCI card" for this purpose. There are no sound cards or anything like that installed. The motherboard has no built-in audio. I can copy all of the possible PCI settings I have in my bios setup and what they are set to, if you think that would be helpful here (I would have done it, but I just am not sure if you are hinting at the possibility there may be something wrong with the BIOS configuration here)? I will say that what you are describing could very well be the case, I've got two disks (one on each of the two built-in controllers) running pretty hot-and-heavy during most of this too. - Greg >A master latency timer value of 32 (0x20) should keep the bus-master >switch overhead down to 20% (i.e. 80% left for data transfers) and >should keep the latency in the range of 1 microsecond per bus-master >(i.e. 5 microseconds if there are 2 Ethernet cards, 2 disk controllers >and one host bridge active at the same time). In that case, each PCI >device could expect to transfer 100 bytes every 5 microseconds. A >buffer of 128 bytes ought to suffice for a fast Ethernet card, in >that case. > ... > >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. > >Regards, STefan >