From owner-freebsd-i386@FreeBSD.ORG Thu Mar 17 06: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 2352D16A4CE for ; Thu, 17 Mar 2005 06:50:06 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id F304443D31 for ; Thu, 17 Mar 2005 06:50:05 +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 j2H6o5gC002915 for ; Thu, 17 Mar 2005 06:50:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j2H6o5aj002914; Thu, 17 Mar 2005 06:50:05 GMT (envelope-from gnats) Date: Thu, 17 Mar 2005 06:50:05 GMT Message-Id: <200503170650.j2H6o5aj002914@freefall.freebsd.org> To: freebsd-i386@FreeBSD.org From: Peter Jeremy Subject: Re: i386/72441: HP Proliant DL380 hangs on reboot with 5.3 X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Peter Jeremy List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Mar 2005 06:50:06 -0000 The following reply was made to PR i386/72441; it has been noted by GNATS. From: Peter Jeremy To: jhb@freebsd.org Cc: Chen Zhao , freebsd-gnats-submit@freebsd.org Subject: Re: i386/72441: HP Proliant DL380 hangs on reboot with 5.3 Date: Thu, 17 Mar 2005 17:49:31 +1100 There was some discussion in -current around the time I submitted the PR and since there's no obvious link, for the record, the following thread is also relevant: http://lists.freebsd.org/pipermail/freebsd-current/2004-October/039938.html My investigating at the time led me to the following: >Adding some printf's shows that the code is getting into cpu_reset_real(). >By this time, all modules and subsystems have been shutdown. All that's >left to do is ask the hardware for a reset. The only problem is that >the hardware doesn't want to play ball. Presumably something the kernel >is doing (apparently associated with loading kernel modules) is disturbing >the hardware state so that reset no longer works. Unfortunately, I no longer have ready access to that machine. On Tue, 2005-Mar-08 12:38:31 -0500, John Baldwin wrote: > I noticed that >your box claims that the only CPU has an APIC ID of 6 which seems odd. I believe the DL380 supports 1 or 2 CPUs. Chen's dmesg shows that the CPUs have APIC id's of 0 (BSP) and 6 (AP). All I can assume is that either HP designed the machine backward or that someone installed the CPU in the wrong socket (assuming that would work). I never looked inside the box and no longer have physical access to it. -- Peter Jeremy