From owner-freebsd-current@FreeBSD.ORG Tue Sep 16 13:18:26 2003 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 1410C16A4B3 for ; Tue, 16 Sep 2003 13:18:26 -0700 (PDT) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7DFF843FE1 for ; Tue, 16 Sep 2003 13:18:24 -0700 (PDT) (envelope-from damian@sentex.net) Received: from pegmatite.sentex.ca (pegmatite.sentex.ca [192.168.42.92]) by lava.sentex.ca (8.12.9/8.12.8) with ESMTP id h8GKIHCk079259; Tue, 16 Sep 2003 16:18:17 -0400 (EDT) (envelope-from damian@sentex.net) Received: by pegmatite.sentex.ca (Postfix, from userid 1001) id 6613F17137; Tue, 16 Sep 2003 16:18:14 -0400 (EDT) Date: Tue, 16 Sep 2003 16:18:14 -0400 From: Damian Gerow To: Nate Lawson Message-ID: <20030916201814.GF66001@sentex.net> References: <20030916115638.U9706@root.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030916115638.U9706@root.org> X-GPG-Key-Id: 0xB841F142 X-GPG-Fingerprint: C7C1 E1D1 EC06 7C86 AF7C 57E6 173D 9CF6 B841 F142 X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . User-Agent: Mutt/1.5.4i X-Virus-Scanned: By Sentex Communications (lava/20020517) cc: current@freebsd.org Subject: Re: ACPI problems with this morning's -CURRENT 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: Tue, 16 Sep 2003 20:18:26 -0000 Thus spake Nate Lawson (nate@root.org) [16/09/03 15:00]: > I'm almost certain your problem is defining MAXMEM to 512 MB. Remove that > from your kernel config and try again. MAXMEM causes all kinds of > problems. If this doesn't solve it, start with the stock GENERIC and add > back in your custom kernel options until it fails. The last option you > add is the faulty one. I was wondering the same thing myself last night actually... I just pulled that line, and it now works. Which is weird -- I have two other 5.1 machines that I have specified MAXMEM in, without any troubles. It's also strange that this would only be brought out with ACPI...? Anyhow, it's working for me now. If anyone feels like further debugging, I'm all game.