From owner-freebsd-acpi@FreeBSD.ORG Wed Feb 8 15:37:07 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 8F56516A428 for ; Wed, 8 Feb 2006 15:37:07 +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 E228443D46 for ; Wed, 8 Feb 2006 15:37:06 +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 8015718 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 k18FaU4d060571; Wed, 8 Feb 2006 10:36:34 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Nate Lawson Date: Wed, 8 Feb 2006 10:36:32 -0500 User-Agent: KMail/1.9.1 References: <43E7D1A2.1030008@o2.pl> <200602071552.33235.jhb@freebsd.org> <43E9A4CA.9090701@root.org> In-Reply-To: <43E9A4CA.9090701@root.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200602081036.34530.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:07 -0000 On Wednesday 08 February 2006 02:59, Nate Lawson wrote: > John Baldwin wrote: > > On Tuesday 07 February 2006 15:13, Donald J. O'Neill wrote: > >>Other things can affect what he's trying to do and cause him to think he > >>has an ACPI problem. I had a bad USB mouse that was causing problems on > >>one of my computers, in fact anything USB on that computer caused a > >>problem with ACPI (it had to be disabled to allow the computer to > >>boot-up) if that mouse was plugged in, until I found the mouse was bad > >>and switched it with one that was ok. On another computer, I could only > >>boot-up if I either disabled ACPI or had the USB mouse unplugged. After > >>it was up, the mouse could be plugged back in and it would work, ACPI > >>would work, but I would be left wondering about the situation. I > >>finally decided to just use a PS-2 mouse and wait a while. That works > >>fine, although I hate ball mice. > > > > 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 > > than the highest memory address we found, we just extend the last segment > > of physical memory. However, in the case of modern machines with SMAPs, > > this extension can result in including memory that was specifically > > marked as unavailable (because it was in use by the BIOS to store the > > ACPI tables) suddenly being used by the kernel. As part of this process, > > the kernel does test writes to each page, so it would corrupt the ACPI > > tables and eventually lead to issues such as this. > > 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. We don't know we are using ACPI when we do the maxmem and hw.physmem stuff. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org