From owner-freebsd-current@FreeBSD.ORG  Tue Sep 16 13:23:34 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 F1E3216A4B3
	for <current@freebsd.org>; Tue, 16 Sep 2003 13:23:34 -0700 (PDT)
Received: from rootlabs.com (root.org [67.118.192.226])
	by mx1.FreeBSD.org (Postfix) with SMTP id 6C55543FA3
	for <current@freebsd.org>; Tue, 16 Sep 2003 13:23:34 -0700 (PDT)
	(envelope-from nate@rootlabs.com)
Received: (qmail 9910 invoked by uid 1000); 16 Sep 2003 20:23:35 -0000
Date: Tue, 16 Sep 2003 13:23:35 -0700 (PDT)
From: Nate Lawson <nate@root.org>
To: Damian Gerow <damian@sentex.net>
In-Reply-To: <20030916201814.GF66001@sentex.net>
Message-ID: <20030916131946.W9900@root.org>
References: <20030916115638.U9706@root.org>
	<20030916201814.GF66001@sentex.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: current@freebsd.org
Subject: Re: ACPI problems with this morning's -CURRENT [SOLVED]
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Sep 2003 20:23:35 -0000

On Tue, 16 Sep 2003, Damian Gerow wrote:
> 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.

It probably has something to do with the virtual/physical gymnastics ACPI
has to do to map its tables into memory.

I have no time to track this down but the output of acpidump -t may help
someone else who might be interested.  You're looking for the pointers
that are stored in RSD PTR.

-Nate