From owner-freebsd-acpi@FreeBSD.ORG Mon Jun 4 19:45:53 2007 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B663216A4C4 for ; Mon, 4 Jun 2007 19:45:53 +0000 (UTC) (envelope-from nate@root.org) Received: from root.org (root.org [67.118.192.226]) by mx1.freebsd.org (Postfix) with ESMTP id 38A9213C487 for ; Mon, 4 Jun 2007 19:45:53 +0000 (UTC) (envelope-from nate@root.org) Received: (qmail 95634 invoked from network); 4 Jun 2007 19:45:54 -0000 Received: from udp166215uds.hawaiiantel.net (HELO ?192.168.1.44?) (nate-mail@72.234.230.74) by root.org with ESMTPA; 4 Jun 2007 19:45:54 -0000 Message-ID: <46646BD3.5080900@root.org> Date: Mon, 04 Jun 2007 12:45:23 -0700 From: Nate Lawson User-Agent: Thunderbird 2.0.0.0 (X11/20070513) MIME-Version: 1.0 To: Peter Holm References: <20070604183419.GA73268@peter.osted.lan> In-Reply-To: <20070604183419.GA73268@peter.osted.lan> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org Subject: Re: Possible ACPI relared panic with Tyan S2720 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: Mon, 04 Jun 2007 19:45:53 -0000 Peter Holm wrote: > I have a panic that comes and go. Kostik has helped me narrow the > problem down to AcpiOsWritePort(). > > It is not a problem for me, as there are various was to work around > it. > > More info can be found here: http://people.freebsd.org/~pho/acpi.html Thanks for all your debugging effort. This is a really confusing issue. All the trace you have shows is that it occurs while transitioning the system from legacy to ACPI mode. Unfortunately, the details of what is going on are hidden in the BIOS since that write to a port triggers an SMI and the BIOS does the rest. However, it seems like the BIOS is reserving more memory, using memory it didn't reserve, or FreeBSD is using memory we shouldn't. John, any insight on the SMAP output? > SMAP type=01 base=0000000000000000 len=000000000009fc00 > SMAP type=02 base=000000000009fc00 len=0000000000000400 > SMAP type=02 base=00000000000e0000 len=0000000000020000 > SMAP type=01 base=0000000000100000 len=000000003fef0000 > SMAP type=03 base=000000003fff0000 len=000000000000f000 > SMAP type=04 base=000000003ffff000 len=0000000000001000 > SMAP type=02 base=00000000fec00000 len=0000000000100000 > SMAP type=02 base=00000000fee00000 len=0000000000001000 > SMAP type=02 base=00000000fff80000 len=0000000000080000 Peter, can you figure out what phys address is getting overwritten? Seems like it's the loader that sets up the module list and the loader's allocator may be using RAM it shouldn't. -- Nate