From owner-freebsd-stable@FreeBSD.ORG Fri Sep 12 15:23:10 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 3150516A4BF for ; Fri, 12 Sep 2003 15:23:10 -0700 (PDT) Received: from blake.polstra.com (mail.polstra.com [206.213.73.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id F029644003 for ; Fri, 12 Sep 2003 15:23:00 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from strings.polstra.com (strings.polstra.com [206.213.73.20]) by blake.polstra.com (8.12.9/8.12.9) with ESMTP id h8CMMnZj032238; Fri, 12 Sep 2003 15:22:49 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20030912221950.GA84689@freebsd1.cimlogic.com.au> Date: Fri, 12 Sep 2003 15:22:49 -0700 (PDT) From: John Polstra To: John Birrell X-Bogosity: No, tests=bogofilter, spamicity=0.491473, version=0.14.5 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:23:10 -0000 On 12-Sep-2003 John Birrell wrote: > 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. On the board that fails, have you tried disabling ACPI in /boot/loader.conf or at the loader prompt? It would be interesting to see whether that made a difference. John