From owner-freebsd-i386@FreeBSD.ORG Fri Mar 18 17:50:06 2005 Return-Path: Delivered-To: freebsd-i386@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 73A5616A4CE for ; Fri, 18 Mar 2005 17:50:06 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49F4143D46 for ; Fri, 18 Mar 2005 17:50:06 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j2IHo6Pp084648 for ; Fri, 18 Mar 2005 17:50:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j2IHo5kD084647; Fri, 18 Mar 2005 17:50:06 GMT (envelope-from gnats) Date: Fri, 18 Mar 2005 17:50:06 GMT Message-Id: <200503181750.j2IHo5kD084647@freefall.freebsd.org> To: freebsd-i386@FreeBSD.org From: weechris Subject: Re: i386/78339: BTX loader crashes on boot on HP Proliant DL140 X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: weechris List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Mar 2005 17:50:06 -0000 The following reply was made to PR i386/78339; it has been noted by GNATS. From: weechris To: freebsd-gnats-submit@FreeBSD.org Cc: Subject: Re: i386/78339: BTX loader crashes on boot on HP Proliant DL140 Date: Fri, 18 Mar 2005 09:43:40 -0800 Can anyone tell me if this problem is the result of a spurious interrupt? We seem to have much better luck booting with the network cables disconnected. I'm wondering if the problem is that a Wake-ON-LAN interrupt or other interrupt arrives before the boot loader has a chance to install interrupt handlers. However, even disabling WOL in the Broadcom config screen and disabling PXEboot does not prevent the problem from happening. we're trying to follow up with HP as well. The problem occurs more frequently under bios 04502T03 than bios 3304T03 2/2/2004. we have it happening on at least 3 DL140s. -chris