From owner-freebsd-acpi@FreeBSD.ORG Wed Feb 8 09:33:38 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 0D6A016A420; Wed, 8 Feb 2006 09:33:38 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from mail17.syd.optusnet.com.au (mail17.syd.optusnet.com.au [211.29.132.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A0B343D58; Wed, 8 Feb 2006 09:33:36 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail17.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k189XWYv009337 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 8 Feb 2006 20:33:33 +1100 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.4/8.13.4) with ESMTP id k189XWHS001351; Wed, 8 Feb 2006 20:33:32 +1100 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.4/8.13.4/Submit) id k189XWE3001350; Wed, 8 Feb 2006 20:33:32 +1100 (EST) (envelope-from peter) Date: Wed, 8 Feb 2006 20:33:32 +1100 From: Peter Jeremy To: Nate Lawson Message-ID: <20060208093332.GA702@turion.vk2pj.dyndns.org> References: <43E7D1A2.1030008@o2.pl> <200602071404.44314.jhb@freebsd.org> <200602071413.07109.duncan.fbsd@gmail.com> <200602071552.33235.jhb@freebsd.org> <43E9A4CA.9090701@root.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43E9A4CA.9090701@root.org> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 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 09:33:38 -0000 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. -- Peter Jeremy