From owner-freebsd-i386@FreeBSD.ORG Thu Feb 17 06:50:53 2005 Return-Path: Delivered-To: freebsd-i386@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DBFFC16A4CE for ; Thu, 17 Feb 2005 06:50:53 +0000 (GMT) Received: from mail11.syd.optusnet.com.au (mail11.syd.optusnet.com.au [211.29.132.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F26F43D48 for ; Thu, 17 Feb 2005 06:50:53 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) j1H6om4e030695 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 17 Feb 2005 17:50:50 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])j1H6om7l075673; Thu, 17 Feb 2005 17:50:48 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)j1H6olGF075672; Thu, 17 Feb 2005 17:50:47 +1100 (EST) (envelope-from pjeremy) Date: Thu, 17 Feb 2005 17:50:47 +1100 From: Peter Jeremy To: "Charles A. Newcomer" Message-ID: <20050217065047.GA75636@cirb503493.alcatel.com.au> References: <2eac5164188fa4a3caa75e1f9f7ef65b@iapc.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2eac5164188fa4a3caa75e1f9f7ef65b@iapc.net> User-Agent: Mutt/1.4.2i cc: freebsd-i386@freebsd.org Subject: Re: Problem Report i386/72441 X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Feb 2005 06:50:54 -0000 On Wed, 2005-Feb-16 11:47:33 -0600, Charles A. Newcomer wrote: >Upgrading to the latest DL380 Firmware should solve this problem. > >> A DL380 running FreeBSD 5 will not automatically reboot after >> a 'reboot' command or panic. It hangs at the 'Rebooting...' >> message and must be powered off/on to recover. The system was running the latest firmware available at the time I submitted the PR. Upgrading the firmware now would be inconvenient (or worse) and I would need something more definite than "should solve the problem" before attempting it. Can you explain why you believe that the latest firmware will fix the problem and what version of firmware contains the fix. -- Peter Jeremy