From owner-freebsd-acpi@FreeBSD.ORG Wed Feb 8 15:37:19 2006 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 970C116A420 for ; Wed, 8 Feb 2006 15:37:19 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 27BA043D5A for ; Wed, 8 Feb 2006 15:37:14 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 8015716 for multiple; Wed, 08 Feb 2006 10:35:46 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k18FaU4c060571; Wed, 8 Feb 2006 10:36:31 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Peter Jeremy Date: Wed, 8 Feb 2006 10:36:07 -0500 User-Agent: KMail/1.9.1 References: <43E7D1A2.1030008@o2.pl> <43E9A4CA.9090701@root.org> <20060208093332.GA702@turion.vk2pj.dyndns.org> In-Reply-To: <20060208093332.GA702@turion.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200602081036.09619.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1280/Tue Feb 7 05:11:53 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: freebsd-acpi@freebsd.org Subject: Re: Kernel panic with ACPI enabled X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Feb 2006 15:37:19 -0000 On Wednesday 08 February 2006 04:33, Peter Jeremy wrote: > On Tue, 2006-Feb-07 23:59:06 -0800, Nate Lawson wrote: > >John Baldwin wrote: > >>Actually, in his case I'm fairly sure MAXMEM is the problem. Several > >>people have had problems trying to use the tunable equivalent > >>(hw.physmem=3g and the like) because if the new maxmem value is greater > > > >Can we at least put a printf() in the boot sequence that says "warning: > >maxmem set and acpi enabled, this may cause problems"? This keeps > >coming up. > > Presumably this isn't a problem where hw.physmem is used to artifically > reduce the system for testing. It depends on the value you use. Some values will be ok, some will break things. The code that handles maxmem and physmem really needs to be SMAP-aware and not use memory that we know isn't really memory. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org