From owner-freebsd-stable Mon Feb 26 14:30:43 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.panix.com (mail2.panix.com [166.84.0.213]) by hub.freebsd.org (Postfix) with ESMTP id EC5F237B65D for ; Mon, 26 Feb 2001 14:30:37 -0800 (PST) (envelope-from evenson@panix.com) Received: from panix6.panix.com (panix6.panix.com [166.84.0.231]) by mail2.panix.com (Postfix) with ESMTP id 0179D9557; Mon, 26 Feb 2001 17:26:06 -0500 (EST) Received: (from evenson@localhost) by panix6.panix.com (8.8.8/8.7.1/PanixN1.0) id RAA07227; Mon, 26 Feb 2001 17:26:05 -0500 (EST) X-Authentication-Warning: panix6.panix.com: evenson set sender to evenson@panix.com using -f To: remy@boostworks.com Cc: stable@freebsd.org Subject: Re: fxp0: SCB timeout References: <200102232030.VAA66739@luxren2.boostworks.com> From: Mark Evenson Date: 26 Feb 2001 17:26:05 -0500 In-Reply-To: Remy Nonnenmacher's message of "Fri, 23 Feb 2001 21:32:07 +0100 (CET)" Message-ID: Lines: 49 User-Agent: Gnus/5.0805 (Gnus v5.8.5) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Remy Nonnenmacher writes: > Hello, > > I recently upgraded a machine from 4.2-RELEASE (was working fine) to > 4.2-STABLE and i now get messages from fxp driver: > > fxp0: SCB timeout > > this hangs nfs but network keeps going on (with some short pauses > anyway). The motherboard is an Intel STL2, running SMP, with integrated > 82559 chip. > I ran into the same problem on a Dell Dimension 4100 whose onboard Ethernet is reported via dmesg as fxp0: port 0xdf00-0xdf3f mem 0xfeaff000-0xfeafffff irq 3 at device 8.0 on pci2 fxp0: Ethernet address 00:03:47:0e:70:be And by support.dell.com with my service tag as: Integrated Intel 10/100 Ethernet Controller Driver (Intel 82562ET chip set) This error would occur at a random interval after the network interface was brought up and used, usually within ten minutes. The failure seemed to correspond loosely to the number of packets that were pumped through the interface. The failure was a total lack of IP traffic until rebooted, not just some network traffic. I slapped a rather old PCI fxp card in the box that I had lying around my house to get around the problem, which works fine. Since I am running this hardware as a contract Java programmer, I can't really justify spending the time to go through the drivers to figure out what is wrong. This error occurs both on 4_2_RELEASE (which I installed) and 4_STABLE (which I am tracking currently). I would gladly serve as a test point if someone develops code that they think addresses this problem. -- Mark Evenson "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message