From owner-freebsd-acpi@FreeBSD.ORG Tue Jun 5 14:31:25 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 DB4D216A400 for ; Tue, 5 Jun 2007 14:31:25 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.freebsd.org (Postfix) with ESMTP id 5FB8713C44C for ; Tue, 5 Jun 2007 14:31:25 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id l55EUsTb028249; Tue, 5 Jun 2007 10:31:12 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Nate Lawson Date: Tue, 5 Jun 2007 10:27:29 -0400 User-Agent: KMail/1.9.6 References: <20070604183419.GA73268@peter.osted.lan> <20070605043758.GA99622@peter.osted.lan> <46652286.2040006@root.org> In-Reply-To: <46652286.2040006@root.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200706051027.29879.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Tue, 05 Jun 2007 10:31:13 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/3360/Tue Jun 5 00:32:46 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx 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: Tue, 05 Jun 2007 14:31:25 -0000 On Tuesday 05 June 2007 04:44:54 am Nate Lawson wrote: > Peter Holm wrote: > > On Mon, Jun 04, 2007 at 12:45:23PM -0700, Nate Lawson wrote: > >> 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. > >> > > > > If I did it right (I used a vtophys() on the address): > > > > Address of mod->name(if_tun): 0xc3eed5ec, phys: 0x985ec > > So it's somewhere near 620K and the first region goes to 640K - 1 K. > The last 1 K is type 2 (reserved). Nothing seems to show why switching > to acpi mode results in an overwrite of data at 620K. I'm not sure > where to look. > > There should be some way to write a guard pattern to that area but I'll > have to think about it a bit first. Can you see if a BIOS update is > available and try it out? What about seeing if you can pre-alloc (by > hacking loader's SMAP code to reserve more of the first 640 K) and > writing a pattern there, then verifying it at various points during boot > to be sure we know exactly where the BIOS is writing? Err, the loader should not be storing modules that low. Did you kldload the module or load it via the loader? -- John Baldwin