From owner-freebsd-current Sat Nov 16 12:30:16 2002 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 A96A237B401; Sat, 16 Nov 2002 12:30:14 -0800 (PST) Received: from dibbler.ne.client2.attbi.com (dibbler.ne.client2.attbi.com [24.61.41.247]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D7D143E6E; Sat, 16 Nov 2002 12:30:11 -0800 (PST) (envelope-from rodrigc@attbi.com) Received: from dibbler.ne.client2.attbi.com (localhost [127.0.0.1]) by dibbler.ne.client2.attbi.com (8.12.6/8.12.6) with ESMTP id gAGKU9O8016410; Sat, 16 Nov 2002 15:30:11 -0500 (EST) (envelope-from rodrigc@dibbler.ne.client2.attbi.com) Received: (from rodrigc@localhost) by dibbler.ne.client2.attbi.com (8.12.6/8.12.6/Submit) id gAGKU6eA016409; Sat, 16 Nov 2002 15:30:06 -0500 (EST) Date: Sat, 16 Nov 2002 15:30:05 -0500 From: Craig Rodrigues To: Anders Andersson Cc: freebsd-current@freebsd.org, jhb@freebsd.org Subject: Re: bad ACPI Message-ID: <20021116153005.A16366@attbi.com> References: <20021116161342.GD1509@hellraiser.example.org> <30665.1037463559@critter.freebsd.dk> <20021116162315.GF1509@hellraiser.example.org> <20021116113549.A849@attbi.com> <20021116164401.GG1509@hellraiser.example.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20021116164401.GG1509@hellraiser.example.org>; from anders@hack.org on Sat, Nov 16, 2002 at 05:44:01PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Nov 16, 2002 at 05:44:01PM +0100, Anders Andersson wrote: > On Sat, Nov 16, 2002 at 11:35:49AM -0500, Craig Rodrigues wrote: > > Could you try the following? > > > > At the boot prompt, before the kernel boots up: > > > > unset acpi_load > > set boot_verbose=YES > > boot -v > > OK, now I feel stupid since I could swear that I already did try to > disable ACPI. > > But with ACPI disabled it boots fine. > > phk, sorry to confuse you :-) I had a very similar problem. I had a system here which would crash upon bootup when acpi was loaded. Since I couldn't boot into the system to read the man pages, I didn't know what to do. At the boot prompt, I typed show. It clearly listed: acpi_load=YES I then typed: set acpi_load=NO boot Of course, the system still tried to load acpi, and crashed. The correct thing to do would have been to read loader(8), and deduce that it would be necessary to unset acpi_load in order to not load acpi. This tripped me up, and might trip other new users who try 5.0. Would a patch of this sort be something to consider? --- sys/boot/i386/libi386/i386_module.c.orig Sat Nov 16 15:01:07 2002 +++ sys/boot/i386/libi386/i386_module.c Sat Nov 16 15:20:04 2002 @@ -57,7 +57,8 @@ disabled = 1; } - if (getenv("acpi_load") && (!disabled)) { + rv = getenv("acpi_load"); + if (rv != NULL && (!disabled) && (strcasecmp(rv,"NO") != 0)) { error = mod_load("acpi", NULL, 0, NULL); if (error != 0) printf("ACPI autoload failed - %s\n", strerror(error)); -- Craig Rodrigues http://www.gis.net/~craigr rodrigc@attbi.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message