From owner-freebsd-amd64@FreeBSD.ORG Wed Jan 25 23:00:08 2012 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 512EE106566B for ; Wed, 25 Jan 2012 23:00:08 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 2BE298FC16 for ; Wed, 25 Jan 2012 23:00:08 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q0PN08vi014833 for ; Wed, 25 Jan 2012 23:00:08 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0PN08lf014832; Wed, 25 Jan 2012 23:00:08 GMT (envelope-from gnats) Date: Wed, 25 Jan 2012 23:00:08 GMT Message-Id: <201201252300.q0PN08lf014832@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Andriy Gapon X-Mailman-Approved-At: Thu, 26 Jan 2012 00:00:02 +0000 Cc: Subject: Re: amd64/164457: [install] Can't install FreeBSD 9.0 (amd64) on HP Blade (ProLiant BL465c G1 ) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Andriy Gapon List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2012 23:00:08 -0000 The following reply was made to PR amd64/164457; it has been noted by GNATS. From: Andriy Gapon To: bug-followup@FreeBSD.org, a@jenisch.at Cc: Subject: Re: amd64/164457: [install] Can't install FreeBSD 9.0 (amd64) on HP Blade (ProLiant BL465c G1 ) Date: Thu, 26 Jan 2012 00:45:23 +0200 First, there is probably no point in trying to boot without ACPI support on modern systems. Most likely "Safe mode" is just equivalent to "ACPI off" for the installation media. Second, it's surprising the Verbose option doesn't result in more verbose boot messages. Could you please re-test this? I suspect that your problem might be related to the recent eventtimers changes. Could you please try playing with setting the following tunables on the loader prompt (via 'set' command)? kern.eventtimer.periodic=1 kern.eventtimer.timer="LAPIC" -- Andriy Gapon