From owner-freebsd-current@FreeBSD.ORG Fri Dec 3 05:55:56 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E7E0716A4CE for ; Fri, 3 Dec 2004 05:55:56 +0000 (GMT) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9624A43D48 for ; Fri, 3 Dec 2004 05:55:56 +0000 (GMT) (envelope-from ken@nargothrond.kdm.org) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.12.11/8.12.11) with ESMTP id iB35tsSD061851; Thu, 2 Dec 2004 22:55:54 -0700 (MST) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.12.11/8.12.5/Submit) id iB35ts90061850; Thu, 2 Dec 2004 22:55:54 -0700 (MST) (envelope-from ken) Date: Thu, 2 Dec 2004 22:55:54 -0700 From: "Kenneth D. Merry" To: Andrew Gallatin Message-ID: <20041203055554.GA61823@nargothrond.kdm.org> References: <20041130035552.GA32924@nargothrond.kdm.org> <16812.29117.221988.730885@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <16812.29117.221988.730885@grasshopper.cs.duke.edu> User-Agent: Mutt/1.4.2i X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c on nargothrond.kdm.org X-Virus-Status: Clean cc: current@FreeBSD.org Subject: Re: -current hang during boot on SMP machine X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 05:55:57 -0000 On Tue, Nov 30, 2004 at 08:12:29 -0500, Andrew Gallatin wrote: > > Have you tried disabling ACPI via hint.acpi.0.disabled="1" in > /boot/loader.conf > > The ACPI on these older machines is pretty bad. I have a very similar > SuperMicro machine w/o SCSI at work which runs 5.3-R fine w/ACPI > disabled. I discovered early in the 5.0 cycle that enabling ACPI > would lead to a console message for each fxp0 interrupt.. FWIW, with -current from today (December 2nd), I can boot with ACPI enabled and things seem to work. Ken -- Kenneth Merry ken@FreeBSD.org