From owner-freebsd-stable@FreeBSD.ORG Fri Sep 12 15:17:01 2003 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 2171616A4BF for ; Fri, 12 Sep 2003 15:17:01 -0700 (PDT) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73A9643FE9 for ; Fri, 12 Sep 2003 15:16:57 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: from freebsd1.cimlogic.com.au (localhost [127.0.0.1]) by cimlogic.com.au (8.12.9/8.12.9) with ESMTP id h8CMJsbZ090117; Sat, 13 Sep 2003 08:19:54 +1000 (EST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by freebsd1.cimlogic.com.au (8.12.9/8.12.9/Submit) id h8CMJoOP090116; Sat, 13 Sep 2003 08:19:51 +1000 (EST) Date: Sat, 13 Sep 2003 08:19:50 +1000 From: John Birrell To: John Polstra Message-ID: <20030912221950.GA84689@freebsd1.cimlogic.com.au> References: <6.0.0.22.0.20030912134112.05891060@209.112.4.2> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i cc: Info Account cc: freebsd-stable@freebsd.org Subject: Re: recent stability problems with fxp driver 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: Fri, 12 Sep 2003 22:17:01 -0000 On Fri, Sep 12, 2003 at 01:51:56PM -0700, John Polstra wrote: > The problem is real, at least on some hardware. I had to give up on > using the two integrated fxp devices on my Dell 1550 -- which is a > real bummer, since it's a 1U box that only has two PCI slots. With > the latest -stable driver, I couldn't fetch a 560 MB file from > another machine on the LAN using FTP without killing the fxp device. I'm suffering what seem like different problems with the fxp driver. In RELENG_4 the driver works well on two different embedded boards that I have. On one of those boards I regularly transfer ~500 MB files [via HTTP 8-)] and the driver appears stable. As soon as I try to run -current on one of those boards, the kernel hangs in fxp's attach, just after the IRQ resource is allocated, and possibly just when the driver tries to reset the board. I haven't been able to debug this. I wonder if the device is creating an interrupt storm. I have a hard time believing that the BIOS is behaving any differently when booting a RELENG_4 kernel compared to a current one. Certainly the probe output for fxp is the same. When I try the same -current kernel on the other embedded board, it works. The boards are very different. One has a Cyrix processor and the other is an AMD Elan SC520. They both have a General Software bios, but obviously the different processors make that largely irrelevant. What makes my situation even more confusing is that the -current kernel that hangs attaching fxp, was actually netbooted over the device that it hangs attaching. I'm tempted to conclude that it isn't rogue hardware - just a situation that isn't catered for FreeBSD. I wish I knew how to debug it. -- John Birrell