From owner-freebsd-stable Wed May 8 3:30:39 2002 Delivered-To: freebsd-stable@freebsd.org Received: from luxren2.boostworks.com (luxren2.boostworks.com [194.167.81.214]) by hub.freebsd.org (Postfix) with ESMTP id A838237B406 for ; Wed, 8 May 2002 03:30:32 -0700 (PDT) Received: from boostworks.com (rn.lxlun.boostworks.com [192.168.8.100]) by luxren2.boostworks.com (8.11.3/8.11.3) with ESMTP id g48AUIs10030; Wed, 8 May 2002 12:30:20 +0200 (CEST) Message-Id: <200205081030.g48AUIs10030@luxren2.boostworks.com> Date: Wed, 8 May 2002 12:26:27 +0200 (CEST) From: remy@boostworks.com Subject: Re: fxp0: SCB timeout To: dwhite@resnet.uoregon.edu Cc: stable@FreeBSD.ORG In-Reply-To: <20020507142539.N90778-100000@resnet.uoregon.edu> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 7 May, Doug White wrote: > On Tue, 7 May 2002 remy@boostworks.com wrote: > >> On 6 May, Paul Dlug wrote: >> > >> > If the general consensus is that adding a PCI NIC and disabling the >> > onboard will fix it, I'll go that route. But I'd rather try to >> > understand what the actual problem is and hopefully get a fix for >> > it. Does anyone have suggestions for further debugging? >> > >> >> I spent around a week, a month ago, trying to understand the problem. >> If it may help, here is the tale: >> >> The machine is an Intel SCB2 (SMP, ServerWorks HE-SL based) with a 64 >> Bits/66Mhz PCI NIC using a 21154BC transparent PCI bridge and two 82559 >> A0 revision chips. > > Funny you mention the SCB2. The BMC hooks the NIC looking for > management packets on this board (and other IPMI-equipped > motherboards). I've gotten large numbers of SCB timeouts when > communicating with the BMC this way. So it might just be the NIC is > being grabbed for another purpose and the driver is sensitive to this. > > Note I have not seen any performance degredation as a result, although > I haven't done large amounts of testing. > > Doug White | FreeBSD: The Power to Serve > dwhite@resnet.uoregon.edu | www.FreeBSD.org > IIRC, there have been notice that some IPMI releases were using TCO force mode in specific cases. This means that the 82559 or 82550 is 'reserved' for SMBus transactions and do not send regular packets in the transmit ring (hence the timeouts). BTW, many many thanks, Doug, for your work about IPMI. Reading the SEL records from FBSD is a lot more efficient than hooking a keyboard and a mouse, booting on the support CD and dealing with the Windows 3.11 like interface. RN. IhM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message