From owner-freebsd-acpi@FreeBSD.ORG Tue Feb 7 23:09: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 ED59F16A420 for ; Tue, 7 Feb 2006 23:09:07 +0000 (GMT) (envelope-from p-celej@o2.pl) Received: from poczta.o2.pl (mx2.go2.pl [193.17.41.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 81C9043D46 for ; Tue, 7 Feb 2006 23:09:07 +0000 (GMT) (envelope-from p-celej@o2.pl) Received: from [192.168.0.25] (unknown [80.50.246.86]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by poczta.o2.pl (Postfix) with ESMTP id 0EBAB7480CB for ; Wed, 8 Feb 2006 00:09:06 +0100 (CET) Message-ID: <43E928C0.5050104@o2.pl> Date: Wed, 08 Feb 2006 00:09:52 +0100 From: =?ISO-8859-2?Q?Przemys=B3aw_Celej?= User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: freebsd-acpi@freebsd.org References: <43E7D1A2.1030008@o2.pl> <200602071404.44314.jhb@freebsd.org> <200602071413.07109.duncan.fbsd@gmail.com> <200602071552.33235.jhb@freebsd.org> In-Reply-To: <200602071552.33235.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 8bit 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: Tue, 07 Feb 2006 23:09:08 -0000 John Baldwin wrote: > On Tuesday 07 February 2006 15:13, Donald J. O'Neill 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 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. > > Exactly ! I removed MAXMEM option, and: NO_MEMORY_HOLE , CPU_UPGRADE_HW_CACHE, CPU_FASTER_5X86_FPU, CPU_SUSP_HLT, CPU_ATHLON_SSE_HACK. And ACPI now works perfectly. Huge thanks. -- Pozdrawiam Przemysław Celej