From owner-freebsd-acpi@FreeBSD.ORG Mon Jun 4 11:08:17 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 0BC8016A473 for ; Mon, 4 Jun 2007 11:08:17 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id D3AB213C465 for ; Mon, 4 Jun 2007 11:08:16 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l54B8GKY037418 for ; Mon, 4 Jun 2007 11:08:16 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l54B8Fte037414 for freebsd-acpi@FreeBSD.org; Mon, 4 Jun 2007 11:08:15 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 4 Jun 2007 11:08:15 GMT Message-Id: <200706041108.l54B8Fte037414@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-acpi@FreeBSD.org Cc: Subject: Current problem reports assigned to you 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 11:08:17 -0000 Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o i386/54756 acpi ACPI suspend/resume problem on CF-W2 laptop o i386/55661 acpi ACPI suspend/resume problem on ARMADA M700 o kern/55822 acpi No ACPI power off with SMP kernel o kern/56024 acpi ACPI suspend drains battery while in S3 o i386/64002 acpi acpi problem o i386/67273 acpi [hang] system hangs with acpi and Xfree o i386/72566 acpi ACPI, FreeBSD disables fan on Compaq Armada 1750 f kern/73221 acpi acpi suspend ATI mobility 9000 s i386/79080 acpi acpi thermal changes freezes HP nx6110 o i386/79081 acpi ACPI suspend/resume not working on HP nx6110 s i386/91748 acpi acpi problem on Acer TravelMare 4652LMi (nvidia panic, o kern/102252 acpi acpi thermal does not work on Abit AW8D (intel 975) o kern/104625 acpi ACPI on ASUS A8N-32 SLI/ASUS P4P800 does not show ther o kern/106924 acpi [acpi] ACPI resume returns g_vfs_done() errors and ker 14 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/67309 acpi zzz reboot computer (ACPI S3) o i386/69750 acpi Boot without ACPI failed on ASUS L5 o i386/72179 acpi [acpi] [patch] Inconsistent apm(8) output regarding th o kern/73823 acpi [feature request] acpi / power-on by timer support f kern/74868 acpi [acpi] ACPI enabled in 5.3 Release make Kernel reboot o kern/76950 acpi ACPI wrongly blacklisted on Micron ClientPro 766Xi sys o kern/89411 acpi [acpi] acpiconf bug f kern/90871 acpi ACPI problems with ASUS A8N-VM-CSM o kern/97383 acpi Volume buttons on IBM Thinkpad crash system with ACPI o i386/97468 acpi [acpi] ACPI on ASUS A7V hangs on shutdown -p (power of o kern/98171 acpi [acpi] ACPI 1304 / 0501 errors on Acer 5024WLMi Laptop o kern/103365 acpi [acpi] acpi poweroff doesn't work with geli device att o kern/105537 acpi [acpi] problems in acpi on HP Compaq nc6320 o kern/108017 acpi [acpi]: Acer Aspire 5600 o kern/108488 acpi [acpi] ACPI-1304: *** Error: Method execution failed o kern/108581 acpi [sysctl] sysctl: hw.acpi.cpu.cx_lowest: Invalid argume o kern/108695 acpi [acpi]: Fatal trap 9: general protection fault when in f kern/109207 acpi ACPI Problem o kern/111591 acpi [acpi] dev.acpi_ibm.0.events returns I/O error (regres o kern/112544 acpi [acpi] [patch] Add High Precision Event Timer Driver f 20 problems total. From owner-freebsd-acpi@FreeBSD.ORG Mon Jun 4 17:48:28 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 9C99216A400 for ; Mon, 4 Jun 2007 17:48:28 +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 EE9DF13C4AD for ; Mon, 4 Jun 2007 17:48:27 +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 l54HmOrk020896; Mon, 4 Jun 2007 13:48:24 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-acpi@freebsd.org Date: Mon, 4 Jun 2007 11:19:25 -0400 User-Agent: KMail/1.9.6 References: <24393ae80705172026u6194f11esc525d52470aa71f9@mail.gmail.com> <24393ae80705290916i7962bfaak62ea867494d2e77b@mail.gmail.com> <24393ae80706012112he0e2a96x1e0da9e8f5f6d1b0@mail.gmail.com> In-Reply-To: <24393ae80706012112he0e2a96x1e0da9e8f5f6d1b0@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200706041119.26958.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]); Mon, 04 Jun 2007 13:48:24 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/3349/Mon Jun 4 10:32:21 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: Subject: Re: Computer hangs on reboot 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 17:48:28 -0000 On Saturday 02 June 2007 12:12:14 am Andrey Shuvikov wrote: > On 5/29/07, Andrey Shuvikov wrote: > > On 5/29/07, John Baldwin wrote: > > > On Saturday 26 May 2007 01:14:52 pm Andrey Shuvikov wrote: > > > > I tried to add some debug output to cpu_reset_real() code: > > > > > > > > printf("cpu_reset_real(): before keyboard reset\n"); > > > > outb(IO_KBD + 4, 0xFE); > > > > printf("cpu_reset_real(): after keyboard reset\n"); > > > > > > > > The last two lines I see on the screen when I try to reboot are: > > > > > > > > cpu_reset_real(): before keyboard reset > > > > c > > > > > > > > So the computer is halted but doesn't go to reboot. > > > > > > So what if you disable the keyboard reset and let the other methods happen? > > > > > > -- > > > John Baldwin > > > > > > > I tried to set BROKEN_KEYBOARD_RESET option but nothing changed > > (except that I didn't see these debugging messages, obviously). Is it > > possible that keyboard controller issues the reset signal but the CPU > > waits for something? Or reset pin is disabled somehow? > > > > Tried to investigate further... Added code to print keyboard > controller output port to make sure A20 is open. Got 0x0B. Does it > mean that A20 is really open? If A20 is controlled by some kind of > "Fast A20" option, will keyboard controller still show the right > status? And what else can I check? I believe I/O port 0x92 can gate A20 as well, and that it is only open if both say it is open. Grab a datasheet for an ICH from developer.intel.com to find more details on port 0x92. -- John Baldwin From owner-freebsd-acpi@FreeBSD.ORG Mon Jun 4 17:48:35 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 29F2B16A400 for ; Mon, 4 Jun 2007 17:48:35 +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 7B66413C448 for ; Mon, 4 Jun 2007 17:48:34 +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 l54HmOrl020896; Mon, 4 Jun 2007 13:48:27 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-acpi@freebsd.org Date: Mon, 4 Jun 2007 11:21:08 -0400 User-Agent: KMail/1.9.6 References: <62855.69.61.188.89.1180770401.squirrel@www.kc8onw.net> In-Reply-To: <62855.69.61.188.89.1180770401.squirrel@www.kc8onw.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200706041121.09268.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]); Mon, 04 Jun 2007 13:48:27 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/3349/Mon Jun 4 10:32:21 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: Subject: Re: Unable to install System Control Interrupt handler [20070320] 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 17:48:35 -0000 On Saturday 02 June 2007 03:46:41 am jonathan@kc8onw.net wrote: > I just updated to the latest -current from 6.2 release on an amd64 system > and get the below error > ACPI Exception (evevent-0257): AE_ALREADY_EXISTS, Unable to install System > Control Interrupt handler [20070320] > > I found this thread that discusses it as well but it seems to have mostly > died off without a clear resolution. > http://lists.freebsd.org/mailman/htdig/freebsd-acpi/2005-December/002307.html > > I know the BIOS in this machine is pretty poor but I would like to get it > working. > > Thanks for any help, > Jonathan Try this: Index: local_apic.c =================================================================== RCS file: /usr/cvs/src/sys/amd64/amd64/local_apic.c,v retrieving revision 1.36 diff -u -r1.36 local_apic.c --- local_apic.c 6 Mar 2007 17:16:46 -0000 1.36 +++ local_apic.c 4 Jun 2007 15:20:14 -0000 @@ -977,10 +977,6 @@ struct apic_enumerator *enumerator; int retval, best; - /* We only support built in local APICs. */ - if (!(cpu_feature & CPUID_APIC)) - return; - /* Don't probe if APIC mode is disabled. */ if (resource_disabled("apic", 0)) return; -- John Baldwin From owner-freebsd-acpi@FreeBSD.ORG Mon Jun 4 19:01:01 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 76A4B16A421 for ; Mon, 4 Jun 2007 19:01:01 +0000 (UTC) (envelope-from pho@holm.cc) Received: from relay01.pair.com (relay01.pair.com [209.68.5.15]) by mx1.freebsd.org (Postfix) with SMTP id F06EF13C480 for ; Mon, 4 Jun 2007 19:01:00 +0000 (UTC) (envelope-from pho@holm.cc) Received: (qmail 79059 invoked from network); 4 Jun 2007 18:34:20 -0000 Received: from 83.95.197.164 (HELO peter.osted.lan) (83.95.197.164) by relay01.pair.com with SMTP; 4 Jun 2007 18:34:20 -0000 X-pair-Authenticated: 83.95.197.164 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.6/8.13.6) with ESMTP id l54IYKMF073569; Mon, 4 Jun 2007 20:34:20 +0200 (CEST) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.6/8.13.6/Submit) id l54IYJmH073568; Mon, 4 Jun 2007 20:34:19 +0200 (CEST) (envelope-from pho) Date: Mon, 4 Jun 2007 20:34:19 +0200 From: Peter Holm To: freebsd-acpi@freebsd.org Message-ID: <20070604183419.GA73268@peter.osted.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Cc: Subject: 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:01:01 -0000 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 Regards, -- Peter Holm 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 From owner-freebsd-acpi@FreeBSD.ORG Mon Jun 4 20:17:28 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 49A1616A46C for ; Mon, 4 Jun 2007 20:17:28 +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 CAF3E13C465 for ; Mon, 4 Jun 2007 20:17:27 +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 l54KHPLp021748; Mon, 4 Jun 2007 16:17:25 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Nate Lawson Date: Mon, 4 Jun 2007 16:17:23 -0400 User-Agent: KMail/1.9.6 References: <20070604183419.GA73268@peter.osted.lan> <46646BD3.5080900@root.org> In-Reply-To: <46646BD3.5080900@root.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200706041617.23793.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]); Mon, 04 Jun 2007 16:17:25 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/3349/Mon Jun 4 10:32:21 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: Mon, 04 Jun 2007 20:17:28 -0000 On Monday 04 June 2007 03:45:23 pm Nate Lawson wrote: > 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. The physaddr would be helpful. However, everything the loader is doing should fit into this chunk: > > SMAP type=01 base=0000000000100000 len=000000003fef0000 -- John Baldwin From owner-freebsd-acpi@FreeBSD.ORG Tue Jun 5 02:56:55 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 1AACC16A421 for ; Tue, 5 Jun 2007 02:56:55 +0000 (UTC) (envelope-from mr.hyro@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.170]) by mx1.freebsd.org (Postfix) with ESMTP id 8220C13C448 for ; Tue, 5 Jun 2007 02:56:54 +0000 (UTC) (envelope-from mr.hyro@gmail.com) Received: by ug-out-1314.google.com with SMTP id u2so51016uge for ; Mon, 04 Jun 2007 19:56:53 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=TzR/Yqn81l5qiZvk9yhYdSPqPq/r59NgIqdlDYmBaA8IvccU2h708tBvVUAnN1Nxv9So5U61+xsTpfhxqZ+fZ+AQxyqtpvaaSnZaGOFVahDcqHnR9rMDbEc8LE+X9Qr2LmpTvoHSgwUHa1iN1t+7r2LRlWmvuochl/YPSmxgr3E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Tl6+z2nU9pztlQqh96IQyt8+nmFsdHq35Sf5hf/tZfIv4O36+BriLrzfwUbt2ps4c46C0uk0BntE+PQ7UJqW45LZL9/qpB37vQy6QpcgOjF7CqteoYvM4bFX7jGBF327jle5YvyeiMw3YYeIzf47fp2W1lfe0Cr/z6gujcW00qQ= Received: by 10.82.152.16 with SMTP id z16mr7830087bud.1181012212946; Mon, 04 Jun 2007 19:56:52 -0700 (PDT) Received: by 10.82.191.1 with HTTP; Mon, 4 Jun 2007 19:56:52 -0700 (PDT) Message-ID: <24393ae80706041956g286b1e97jfa649a3a1f530f5a@mail.gmail.com> Date: Mon, 4 Jun 2007 22:56:52 -0400 From: "Andrey Shuvikov" To: freebsd-acpi@freebsd.org In-Reply-To: <200706041119.26958.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <24393ae80705172026u6194f11esc525d52470aa71f9@mail.gmail.com> <24393ae80705290916i7962bfaak62ea867494d2e77b@mail.gmail.com> <24393ae80706012112he0e2a96x1e0da9e8f5f6d1b0@mail.gmail.com> <200706041119.26958.jhb@freebsd.org> Subject: Re: Computer hangs on reboot 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 02:56:55 -0000 On 6/4/07, John Baldwin wrote: > On Saturday 02 June 2007 12:12:14 am Andrey Shuvikov wrote: > > On 5/29/07, Andrey Shuvikov wrote: > > > On 5/29/07, John Baldwin wrote: > > > > On Saturday 26 May 2007 01:14:52 pm Andrey Shuvikov wrote: > > > > > I tried to add some debug output to cpu_reset_real() code: > > > > > > > > > > printf("cpu_reset_real(): before keyboard reset\n"); > > > > > outb(IO_KBD + 4, 0xFE); > > > > > printf("cpu_reset_real(): after keyboard reset\n"); > > > > > > > > > > The last two lines I see on the screen when I try to reboot are: > > > > > > > > > > cpu_reset_real(): before keyboard reset > > > > > c > > > > > > > > > > So the computer is halted but doesn't go to reboot. > > > > > > > > So what if you disable the keyboard reset and let the other methods > happen? > > > > > > > > -- > > > > John Baldwin > > > > > > > > > > I tried to set BROKEN_KEYBOARD_RESET option but nothing changed > > > (except that I didn't see these debugging messages, obviously). Is it > > > possible that keyboard controller issues the reset signal but the CPU > > > waits for something? Or reset pin is disabled somehow? > > > > > > > Tried to investigate further... Added code to print keyboard > > controller output port to make sure A20 is open. Got 0x0B. Does it > > mean that A20 is really open? If A20 is controlled by some kind of > > "Fast A20" option, will keyboard controller still show the right > > status? And what else can I check? > > I believe I/O port 0x92 can gate A20 as well, and that it is only open if both > say it is open. Grab a datasheet for an ICH from developer.intel.com to find > more details on port 0x92. > > -- > John Baldwin > According to Intel documentation keyboard controller and port 0x92 are OR-ed together, which means it's enough to use either one. Anyway I checked 0x92 (which was 0x00) and set it to 0x02. Didn't help. :-( >From the other hand my chipset is not Intel and I found some references to reboot problem for my motherboard under linux in 2002. These references mention some LPC configuration parameters of Sis630 which enable/disable A20 and allow software reset. I downloaded Sis630 datasheet and will check it tomorrow. What I don't understand though is that OpenBSD, which is installed on the same machine doesn't have any problem rebooting... From owner-freebsd-acpi@FreeBSD.ORG Tue Jun 5 04:38:01 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 B915C16A400 for ; Tue, 5 Jun 2007 04:38:01 +0000 (UTC) (envelope-from pho@holm.cc) Received: from relay00.pair.com (relay00.pair.com [209.68.5.9]) by mx1.freebsd.org (Postfix) with SMTP id 7209413C447 for ; Tue, 5 Jun 2007 04:38:01 +0000 (UTC) (envelope-from pho@holm.cc) Received: (qmail 24978 invoked from network); 5 Jun 2007 04:37:59 -0000 Received: from 83.95.197.164 (HELO peter.osted.lan) (83.95.197.164) by relay00.pair.com with SMTP; 5 Jun 2007 04:37:59 -0000 X-pair-Authenticated: 83.95.197.164 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.6/8.13.6) with ESMTP id l554bxRf099794; Tue, 5 Jun 2007 06:37:59 +0200 (CEST) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.6/8.13.6/Submit) id l554bwOI099793; Tue, 5 Jun 2007 06:37:58 +0200 (CEST) (envelope-from pho) Date: Tue, 5 Jun 2007 06:37:58 +0200 From: Peter Holm To: Nate Lawson Message-ID: <20070605043758.GA99622@peter.osted.lan> References: <20070604183419.GA73268@peter.osted.lan> <46646BD3.5080900@root.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46646BD3.5080900@root.org> User-Agent: Mutt/1.4.2.1i 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 04:38:01 -0000 On Mon, Jun 04, 2007 at 12:45:23PM -0700, Nate Lawson wrote: > 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. > You are welcome :-) > 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 - Peter From owner-freebsd-acpi@FreeBSD.ORG Tue Jun 5 08:45: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 8899816A469 for ; Tue, 5 Jun 2007 08:45:25 +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 6C77713C447 for ; Tue, 5 Jun 2007 08:45:25 +0000 (UTC) (envelope-from nate@root.org) Received: (qmail 83958 invoked from network); 5 Jun 2007 08:45:27 -0000 Received: from udp166215uds.hawaiiantel.net (HELO ?192.168.1.44?) (nate-mail@72.234.230.74) by root.org with ESMTPA; 5 Jun 2007 08:45:27 -0000 Message-ID: <46652286.2040006@root.org> Date: Tue, 05 Jun 2007 01:44:54 -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> <46646BD3.5080900@root.org> <20070605043758.GA99622@peter.osted.lan> In-Reply-To: <20070605043758.GA99622@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: Tue, 05 Jun 2007 08:45:25 -0000 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? -- Nate From owner-freebsd-acpi@FreeBSD.ORG Tue Jun 5 10:14:12 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 2CB3F16A41F for ; Tue, 5 Jun 2007 10:14:12 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from relay01.kiev.sovam.com (relay01.kiev.sovam.com [62.64.120.200]) by mx1.freebsd.org (Postfix) with ESMTP id B623A13C457 for ; Tue, 5 Jun 2007 10:14:11 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from [89.162.146.170] (helo=skuns.kiev.zoral.com.ua) by relay01.kiev.sovam.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.60) (envelope-from ) id 1HvVfk-000CWI-Cw for freebsd-acpi@freebsd.org; Tue, 05 Jun 2007 12:49:55 +0300 Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by skuns.kiev.zoral.com.ua (8.14.1/8.14.1) with ESMTP id l559nc0E013669 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 5 Jun 2007 12:49:38 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.1/8.14.1) with ESMTP id l559ncQQ019976; Tue, 5 Jun 2007 12:49:38 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.1/8.14.1/Submit) id l559nbu3019975; Tue, 5 Jun 2007 12:49:37 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 5 Jun 2007 12:49:37 +0300 From: Kostik Belousov To: Nate Lawson Message-ID: <20070605094937.GU2268@deviant.kiev.zoral.com.ua> References: <20070604183419.GA73268@peter.osted.lan> <46646BD3.5080900@root.org> <20070605043758.GA99622@peter.osted.lan> <46652286.2040006@root.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="iskw6J4cuOvZ6IVF" Content-Disposition: inline In-Reply-To: <46652286.2040006@root.org> User-Agent: Mutt/1.4.2.2i X-Virus-Scanned: ClamAV version 0.90.2, clamav-milter version 0.90.2 on skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on skuns.kiev.zoral.com.ua X-Scanner-Signature: 49b91432ac2f6f50aab85e53d3752740 X-DrWeb-checked: yes X-SpamTest-Envelope-From: kostikbel@gmail.com X-SpamTest-Group-ID: 00000000 X-SpamTest-Header: Not Detected X-SpamTest-Info: Profiles 1118 [June 05 2007] X-SpamTest-Info: helo_type=3 X-SpamTest-Method: none X-SpamTest-Rate: 0 X-SpamTest-Status: Not detected X-SpamTest-Status-Extended: not_detected X-SpamTest-Version: SMTP-Filter Version 3.0.0 [0255], KAS30/Release 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 10:14:12 -0000 --iskw6J4cuOvZ6IVF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jun 05, 2007 at 01:44:54AM -0700, 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=3D01 base=3D0000000000000000 len=3D000000000009fc00 > >>> SMAP type=3D02 base=3D000000000009fc00 len=3D0000000000000400 > >>> SMAP type=3D02 base=3D00000000000e0000 len=3D0000000000020000 > >>> SMAP type=3D01 base=3D0000000000100000 len=3D000000003fef0000 > >>> SMAP type=3D03 base=3D000000003fff0000 len=3D000000000000f000 > >>> SMAP type=3D04 base=3D000000003ffff000 len=3D0000000000001000 > >>> SMAP type=3D02 base=3D00000000fec00000 len=3D0000000000100000 > >>> SMAP type=3D02 base=3D00000000fee00000 len=3D0000000000001000 > >>> SMAP type=3D02 base=3D00000000fff80000 len=3D0000000000080000 > >> 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. > >> > >=20 > > If I did it right (I used a vtophys() on the address): > >=20 > > Address of mod->name(if_tun): 0xc3eed5ec, phys: 0x985ec >=20 > 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. >=20 > 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? It looks somewhat fishy. Kernel shall be loaded fully above 1st Mb (at 4Mb, in fact). The overwritten location belongs to the kernel data segment, and shall be not loaded into the low 1Mb. --iskw6J4cuOvZ6IVF Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGZTGxC3+MBN1Mb4gRAqaHAKCCJ1EO/h1ib5zju+hlgDiO2DSLnwCgho+Z SSL0lzZRfj5GarJ8hkySXFI= =AAvy -----END PGP SIGNATURE----- --iskw6J4cuOvZ6IVF-- From owner-freebsd-acpi@FreeBSD.ORG Tue Jun 5 13:21:17 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 1F11016A474 for ; Tue, 5 Jun 2007 13:21:17 +0000 (UTC) (envelope-from pho@holm.cc) Received: from relay02.pair.com (relay02.pair.com [209.68.5.16]) by mx1.freebsd.org (Postfix) with SMTP id C2FFF13C4C5 for ; Tue, 5 Jun 2007 13:21:16 +0000 (UTC) (envelope-from pho@holm.cc) Received: (qmail 52947 invoked from network); 5 Jun 2007 13:21:15 -0000 Received: from 83.95.197.164 (HELO peter.osted.lan) (83.95.197.164) by relay02.pair.com with SMTP; 5 Jun 2007 13:21:15 -0000 X-pair-Authenticated: 83.95.197.164 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.6/8.13.6) with ESMTP id l55DLEkn015389; Tue, 5 Jun 2007 15:21:14 +0200 (CEST) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.6/8.13.6/Submit) id l55DLDqR015388; Tue, 5 Jun 2007 15:21:13 +0200 (CEST) (envelope-from pho) Date: Tue, 5 Jun 2007 15:21:13 +0200 From: Peter Holm To: Nate Lawson Message-ID: <20070605132113.GA14976@peter.osted.lan> References: <20070604183419.GA73268@peter.osted.lan> <46646BD3.5080900@root.org> <20070605043758.GA99622@peter.osted.lan> <46652286.2040006@root.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46652286.2040006@root.org> User-Agent: Mutt/1.4.2.1i 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 13:21:17 -0000 On Tue, Jun 05, 2007 at 01:44:54AM -0700, 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? > I'm somewhat hesitant to update the BIOS on my one and only SMP test box. The BIOS is date 7/10/02, so it *is* old, but has served as a stress test box since August 2005. -- Peter 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 From owner-freebsd-acpi@FreeBSD.ORG Tue Jun 5 15:28:22 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 AFACB16A4F5 for ; Tue, 5 Jun 2007 15:28:22 +0000 (UTC) (envelope-from jonathan@kc8onw.net) Received: from ms-smtp-04.nyroc.rr.com (ms-smtp-04.nyroc.rr.com [24.24.2.58]) by mx1.freebsd.org (Postfix) with ESMTP id 107ED13C57A for ; Tue, 5 Jun 2007 15:28:13 +0000 (UTC) (envelope-from jonathan@kc8onw.net) Received: from mail.kc8onw.net (cpe-72-230-89-31.twcny.res.rr.com [72.230.89.31]) by ms-smtp-04.nyroc.rr.com (8.13.6/8.13.6) with ESMTP id l55FSBXI028472 for ; Tue, 5 Jun 2007 11:28:12 -0400 (EDT) Received: from www.kc8onw.net (localhost [127.0.0.1]) by mail.kc8onw.net (Postfix) with ESMTP id BBD6828453 for ; Tue, 5 Jun 2007 11:28:11 -0400 (EDT) Received: from 69.61.188.89 (SquirrelMail authenticated user jonathan) by www.kc8onw.net with HTTP; Tue, 5 Jun 2007 11:28:11 -0400 (EDT) Message-ID: <63066.69.61.188.89.1181057291.squirrel@www.kc8onw.net> In-Reply-To: <200706051025.33764.jhb@freebsd.org> References: <62855.69.61.188.89.1180770401.squirrel@www.kc8onw.net> <200706041121.09268.jhb@freebsd.org> <55785.69.61.188.89.1181008236.squirrel@www.kc8onw.net> <200706051025.33764.jhb@freebsd.org> Date: Tue, 5 Jun 2007 11:28:11 -0400 (EDT) From: jonathan@kc8onw.net To: freebsd-acpi@freebsd.org User-Agent: SquirrelMail/1.5.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: Symantec AntiVirus Scan Engine Subject: Re: Unable to install System Control Interrupt handler [20070320] 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 15:28:22 -0000 On Tue, June 5, 2007 10:25 am, John Baldwin wrote: > Well, that patch addresses the condition in the thread from the URL. You > must have a different issue. Can you follow-up on the mailing list with a > URL to > a verbose dmesg? As much of the verbose dmesg as I could make myself type is below... ( used "...." to signify incomplete lines) GDB: debug ports: dcons GDB: current port: dcons KDB: debugger backends: ddb gdb SMAP type=01 base=0000000000000000 len=000000000009c400 SMAP type=02 base=000000000009c400 len=0000000000003c00 SMAP type=02 base=00000000000dc000 len=0000000000024000 SMAP type=01 base=0000000000100000 len=000000007fda0000 SMAP type=03 base=000000007fea0000 len=000000000000f000 SMAP type=04 base=000000007feaf000 len=0000000000051000 SMAP type=02 base=000000007ff00000 len=0000000000100000 SMAP type=02 base=00000000fec00000 len=0000000000010000 SMAP type=02 base=00000000fee00000 len=0000000000001000 SMAP type=02 base=00000000ff000000 len=0000000001000000 Copyright (c) 1992-2007 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, .... The Regents of.... FreeBSD is a registered trademark of .... FreeBSD 7.0-CURRENT #1: Mon Jun 4 21:30:15 UTC 2007 root@:/usr/obj/usr/src/sys/GENERIC WARNING: WITNESS option enabled .... Using 32 color for the VM-PQ tuning (0, 0) Preloaded elf kernel "/book/kernel/kernel" at 0xffffffff80b92000 Calibrating clock(s) ... i8254 clock: 1193245 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 3200136296 Hz CPU: Intel(R) Pentium(R) 4 CPU 3.20GHz (3200.14-Mhz K8-class CPU) Origin = "GenuineIntel" Id = 0xf43 Stepping = 3 Features=0xbfebfbff Features2=0x649d AMD Features=0x20100800 usable memory = 2133495808 (2034 MB) Physical memory chunk(s): 0x0000000000001000 - 0x0000000000098fff, 622592 bytes (152 pages) 0x0000000000c8f000 - 0x000000007c259fff, 2039671936 bytes (505291 pages) avail memroy = 2058915840 (11963 MB) ath_rate: version 1.2 .... wlan_amrr: null: random: nfslock: pseudo-device kbd: new array size 4 kdb1 at kdbmux0 mem: io: ath_hal: 0.9.20.3 (AR5210, .... rr232x: RocketRAID 232x controller drvier v1.02 (Jun 4 2007 21:30:04) ACPI: RSPD @ 0X0XFRC40/0X0014 (v 0 PTLTD Thanks, Jonathan P.S. Sorry about the private email I meant to send it to the list but forgot to check the To: before I hit send :P From owner-freebsd-acpi@FreeBSD.ORG Tue Jun 5 16:25:31 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 C11E516A468 for ; Tue, 5 Jun 2007 16:25:31 +0000 (UTC) (envelope-from jonathan@kc8onw.net) Received: from ms-smtp-01.nyroc.rr.com (ms-smtp-01.nyroc.rr.com [24.24.2.55]) by mx1.freebsd.org (Postfix) with ESMTP id 7E64613C468 for ; Tue, 5 Jun 2007 16:25:31 +0000 (UTC) (envelope-from jonathan@kc8onw.net) Received: from mail.kc8onw.net (cpe-72-230-89-31.twcny.res.rr.com [72.230.89.31]) by ms-smtp-01.nyroc.rr.com (8.13.6/8.13.6) with ESMTP id l55GPTO3009714 for ; Tue, 5 Jun 2007 12:25:29 -0400 (EDT) Received: from www.kc8onw.net (localhost [127.0.0.1]) by mail.kc8onw.net (Postfix) with ESMTP id 1D4F028453 for ; Tue, 5 Jun 2007 12:25:29 -0400 (EDT) Received: from 69.61.188.89 (SquirrelMail authenticated user jonathan) by www.kc8onw.net with HTTP; Tue, 5 Jun 2007 12:25:29 -0400 (EDT) Message-ID: <62248.69.61.188.89.1181060729.squirrel@www.kc8onw.net> In-Reply-To: <200706051025.33764.jhb@freebsd.org> References: <62855.69.61.188.89.1180770401.squirrel@www.kc8onw.net> <200706041121.09268.jhb@freebsd.org> <55785.69.61.188.89.1181008236.squirrel@www.kc8onw.net> <200706051025.33764.jhb@freebsd.org> Date: Tue, 5 Jun 2007 12:25:29 -0400 (EDT) From: jonathan@kc8onw.net To: freebsd-acpi@freebsd.org User-Agent: SquirrelMail/1.5.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: Symantec AntiVirus Scan Engine Subject: Re: Unable to install System Control Interrupt handler [20070320] 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 16:25:31 -0000 Not my morning this morning I guess, sorry about the cut off email to the list (apparently possibly multiple copies :( ) A hopefully decent email follows. On Tue, June 5, 2007 10:25 am, John Baldwin wrote: > Well, that patch addresses the condition in the thread from the URL. You > must have a different issue. Can you follow-up on the mailing list with a > URL to > a verbose dmesg? I got a good bit of the way through typing up the dmesg and hit a wrong key and lost it (or sent it :P) so I decided just to take pictures of the screen and post them. I hope thats not too much trouble compared to text. The pictures are at http://www.kc8onw.net/~jonathan/verbose/ and are numbered in order from 1.JPG to 16.JPG . They are full size originals because they were even less readable when I resized them. Thanks, Jonathan P.S. Sorry about the private mail it was supposed to go to the list, I forgot to check the To: before I hit Send. From owner-freebsd-acpi@FreeBSD.ORG Tue Jun 5 16:44:05 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 56D9016A421 for ; Tue, 5 Jun 2007 16:44:05 +0000 (UTC) (envelope-from pho@holm.cc) Received: from relay00.pair.com (relay00.pair.com [209.68.5.9]) by mx1.freebsd.org (Postfix) with SMTP id 0A11513C483 for ; Tue, 5 Jun 2007 16:44:04 +0000 (UTC) (envelope-from pho@holm.cc) Received: (qmail 71246 invoked from network); 5 Jun 2007 16:44:02 -0000 Received: from 83.95.197.164 (HELO peter.osted.lan) (83.95.197.164) by relay00.pair.com with SMTP; 5 Jun 2007 16:44:02 -0000 X-pair-Authenticated: 83.95.197.164 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.6/8.13.6) with ESMTP id l55Gi2oZ021525; Tue, 5 Jun 2007 18:44:02 +0200 (CEST) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.6/8.13.6/Submit) id l55Gi29q021524; Tue, 5 Jun 2007 18:44:02 +0200 (CEST) (envelope-from pho) Date: Tue, 5 Jun 2007 18:44:02 +0200 From: Peter Holm To: John Baldwin Message-ID: <20070605164402.GA18091@peter.osted.lan> References: <20070604183419.GA73268@peter.osted.lan> <20070605043758.GA99622@peter.osted.lan> <46652286.2040006@root.org> <200706051027.29879.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200706051027.29879.jhb@freebsd.org> User-Agent: Mutt/1.4.2.1i 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 16:44:05 -0000 On Tue, Jun 05, 2007 at 10:27:29AM -0400, John Baldwin wrote: > 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? > I did not load the module. It's loaded automatically by the loader. This is my /boot/loader.conf kernel_options="-D" machdep.hyperthreading_allowed=1 hw.ata.atapi_dma=0 -- Peter From owner-freebsd-acpi@FreeBSD.ORG Tue Jun 5 17:27:26 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 AD5FC16A46E for ; Tue, 5 Jun 2007 17:27:26 +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 406BD13C45B for ; Tue, 5 Jun 2007 17:27:26 +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 l55HROuq029442; Tue, 5 Jun 2007 13:27:24 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Peter Holm Date: Tue, 5 Jun 2007 13:26:22 -0400 User-Agent: KMail/1.9.6 References: <20070604183419.GA73268@peter.osted.lan> <200706051027.29879.jhb@freebsd.org> <20070605164402.GA18091@peter.osted.lan> In-Reply-To: <20070605164402.GA18091@peter.osted.lan> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200706051326.22581.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 13:27:24 -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 17:27:26 -0000 On Tuesday 05 June 2007 12:44:02 pm Peter Holm wrote: > On Tue, Jun 05, 2007 at 10:27:29AM -0400, John Baldwin wrote: > > 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? > > > > I did not load the module. It's loaded automatically by the loader. > > This is my /boot/loader.conf > > kernel_options="-D" > machdep.hyperthreading_allowed=1 > hw.ata.atapi_dma=0 Are you sure it isn't loaded by ifconfig during boot and thus via an implicit kldload? The loader only loads modules into memory > KERNLOAD (2MB for PAE, 4MB for non-PAE). -- John Baldwin From owner-freebsd-acpi@FreeBSD.ORG Tue Jun 5 18:18:51 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 B8B1916A41F for ; Tue, 5 Jun 2007 18:18:51 +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 6214A13C45D for ; Tue, 5 Jun 2007 18:18:51 +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 l55IIdkl029762; Tue, 5 Jun 2007 14:18:45 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-acpi@freebsd.org Date: Tue, 5 Jun 2007 14:18:39 -0400 User-Agent: KMail/1.9.6 References: <62855.69.61.188.89.1180770401.squirrel@www.kc8onw.net> In-Reply-To: <62855.69.61.188.89.1180770401.squirrel@www.kc8onw.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200706051418.39948.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 14:18:46 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/3362/Tue Jun 5 13:02:53 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: Subject: Re: Unable to install System Control Interrupt handler [20070320] 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 18:18:51 -0000 On Saturday 02 June 2007 03:46:41 am jonathan@kc8onw.net wrote: > I just updated to the latest -current from 6.2 release on an amd64 system > and get the below error > ACPI Exception (evevent-0257): AE_ALREADY_EXISTS, Unable to install System > Control Interrupt handler [20070320] > > I found this thread that discusses it as well but it seems to have mostly > died off without a clear resolution. > http://lists.freebsd.org/mailman/htdig/freebsd-acpi/2005-December/002307.html > > I know the BIOS in this machine is pretty poor but I would like to get it > working. Add 'device atpic' to your kernel. -- John Baldwin From owner-freebsd-acpi@FreeBSD.ORG Tue Jun 5 18:32:19 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 B15BE16A41F for ; Tue, 5 Jun 2007 18:32:19 +0000 (UTC) (envelope-from pho@holm.cc) Received: from relay03.pair.com (relay03.pair.com [209.68.5.17]) by mx1.freebsd.org (Postfix) with SMTP id 75FCE13C457 for ; Tue, 5 Jun 2007 18:32:19 +0000 (UTC) (envelope-from pho@holm.cc) Received: (qmail 83440 invoked from network); 5 Jun 2007 18:32:17 -0000 Received: from 83.95.197.164 (HELO peter.osted.lan) (83.95.197.164) by relay03.pair.com with SMTP; 5 Jun 2007 18:32:17 -0000 X-pair-Authenticated: 83.95.197.164 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.6/8.13.6) with ESMTP id l55IWHA9024117; Tue, 5 Jun 2007 20:32:17 +0200 (CEST) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.6/8.13.6/Submit) id l55IWHlL024116; Tue, 5 Jun 2007 20:32:17 +0200 (CEST) (envelope-from pho) Date: Tue, 5 Jun 2007 20:32:17 +0200 From: Peter Holm To: John Baldwin Message-ID: <20070605183216.GA23211@peter.osted.lan> References: <20070604183419.GA73268@peter.osted.lan> <200706051027.29879.jhb@freebsd.org> <20070605164402.GA18091@peter.osted.lan> <200706051326.22581.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200706051326.22581.jhb@freebsd.org> User-Agent: Mutt/1.4.2.1i 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 18:32:19 -0000 On Tue, Jun 05, 2007 at 01:26:22PM -0400, John Baldwin wrote: > On Tuesday 05 June 2007 12:44:02 pm Peter Holm wrote: > > On Tue, Jun 05, 2007 at 10:27:29AM -0400, John Baldwin wrote: > > > 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? > > > > > > > I did not load the module. It's loaded automatically by the loader. > > > > This is my /boot/loader.conf > > > > kernel_options="-D" > > machdep.hyperthreading_allowed=1 > > hw.ata.atapi_dma=0 > > Are you sure it isn't loaded by ifconfig during boot and thus via an implicit > kldload? The loader only loads modules into memory > KERNLOAD (2MB for PAE, > 4MB for non-PAE). > No, I'm not sure at all! I have tried to manually load acpi.ko at the loader prompt and also to add acpi_load="YES" to /boot/loader.conf. This still overwrites the if_tun entry in the modules list. Typing unset acpi_load at the loader prompt works and I can then later load acpi: $ kldstat Id Refs Address Size Name 1 1 0xc0400000 889124 kernel $ kldload acpi.ko $ kldstat Id Refs Address Size Name 1 3 0xc0400000 889124 kernel 2 1 0xc48af000 57000 acpi.ko Just to summarize the problem: The memory corruption comes and goes depending on the kernel config file. I first identified the "cause" to be files committed by scottl at 2007/05/14 21:48, which just introduces new malloc types. Right now GENERIC works fine again, but if I remove the newly added: nodevice fwip # IP over FireWire (RFC 2734,3146) nodevice dcons # Dumb console driver nodevice dcons_crom # Configuration ROM for dcons the problem pops up again. -- Peter From owner-freebsd-acpi@FreeBSD.ORG Tue Jun 5 18:37:19 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 601A816A41F for ; Tue, 5 Jun 2007 18:37:19 +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 1835D13C457 for ; Tue, 5 Jun 2007 18:37:17 +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 l55IbCCi029882; Tue, 5 Jun 2007 14:37:13 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Peter Holm Date: Tue, 5 Jun 2007 14:37:09 -0400 User-Agent: KMail/1.9.6 References: <20070604183419.GA73268@peter.osted.lan> <200706051326.22581.jhb@freebsd.org> <20070605183216.GA23211@peter.osted.lan> In-Reply-To: <20070605183216.GA23211@peter.osted.lan> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200706051437.09872.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 14:37:13 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/3362/Tue Jun 5 13:02:53 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 18:37:19 -0000 On Tuesday 05 June 2007 02:32:17 pm Peter Holm wrote: > On Tue, Jun 05, 2007 at 01:26:22PM -0400, John Baldwin wrote: > > On Tuesday 05 June 2007 12:44:02 pm Peter Holm wrote: > > > On Tue, Jun 05, 2007 at 10:27:29AM -0400, John Baldwin wrote: > > > > 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? > > > > > > > > > > I did not load the module. It's loaded automatically by the loader. > > > > > > This is my /boot/loader.conf > > > > > > kernel_options="-D" > > > machdep.hyperthreading_allowed=1 > > > hw.ata.atapi_dma=0 > > > > Are you sure it isn't loaded by ifconfig during boot and thus via an implicit > > kldload? The loader only loads modules into memory > KERNLOAD (2MB for PAE, > > 4MB for non-PAE). > > > No, I'm not sure at all! Err, when is _if_tun.ko_ loaded? Or is it part of the static kernel? -- John Baldwin From owner-freebsd-acpi@FreeBSD.ORG Tue Jun 5 19:21:08 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 8CC1816A468 for ; Tue, 5 Jun 2007 19:21:08 +0000 (UTC) (envelope-from pho@holm.cc) Received: from relay02.pair.com (relay02.pair.com [209.68.5.16]) by mx1.freebsd.org (Postfix) with SMTP id 52FC913C465 for ; Tue, 5 Jun 2007 19:21:08 +0000 (UTC) (envelope-from pho@holm.cc) Received: (qmail 1848 invoked from network); 5 Jun 2007 19:21:06 -0000 Received: from 83.95.197.164 (HELO peter.osted.lan) (83.95.197.164) by relay02.pair.com with SMTP; 5 Jun 2007 19:21:06 -0000 X-pair-Authenticated: 83.95.197.164 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.6/8.13.6) with ESMTP id l55JL5Ov025187; Tue, 5 Jun 2007 21:21:05 +0200 (CEST) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.6/8.13.6/Submit) id l55JL5t5025186; Tue, 5 Jun 2007 21:21:05 +0200 (CEST) (envelope-from pho) Date: Tue, 5 Jun 2007 21:21:04 +0200 From: Peter Holm To: John Baldwin Message-ID: <20070605192104.GA24769@peter.osted.lan> References: <20070604183419.GA73268@peter.osted.lan> <200706051326.22581.jhb@freebsd.org> <20070605183216.GA23211@peter.osted.lan> <200706051437.09872.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200706051437.09872.jhb@freebsd.org> User-Agent: Mutt/1.4.2.1i 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 19:21:08 -0000 On Tue, Jun 05, 2007 at 02:37:09PM -0400, John Baldwin wrote: > On Tuesday 05 June 2007 02:32:17 pm Peter Holm wrote: > > On Tue, Jun 05, 2007 at 01:26:22PM -0400, John Baldwin wrote: > > > On Tuesday 05 June 2007 12:44:02 pm Peter Holm wrote: > > > > On Tue, Jun 05, 2007 at 10:27:29AM -0400, John Baldwin wrote: > > > > > 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? > > > > > > > > > > > > > I did not load the module. It's loaded automatically by the loader. > > > > > > > > This is my /boot/loader.conf > > > > > > > > kernel_options="-D" > > > > machdep.hyperthreading_allowed=1 > > > > hw.ata.atapi_dma=0 > > > > > > Are you sure it isn't loaded by ifconfig during boot and thus via an > implicit > > > kldload? The loader only loads modules into memory > KERNLOAD (2MB for > PAE, > > > 4MB for non-PAE). > > > > > No, I'm not sure at all! > > Err, when is _if_tun.ko_ loaded? Or is it part of the static kernel? > Yes, sorry for my unclear explanations! The initial problem, that started my memory corruption hunt was: panic: module_register_init: module named if_tun not found cpuid = 0 KDB: enter: panic [thread pid 0 tid 0 ] Stopped at kdb_enter+0x32: leave db> bt Tracing pid 0 tid 0 td 0xc0b1a920 kdb_enter(c0a19462,0,c0a18083,c1020d50,0,...) at kdb_enter+0x32 panic(c0a18083,c0a18050,c0a18010,a3,c1020d6c,...) at panic+0x124 module_register_init(c0ad124c,101ec00,101ec00,101e000,1028000,...) at module_register_init+0x8a mi_startup() at mi_startup+0x96 begin() at begin+0x2c This is with this kernel config file: $ cat /usr/src/sys/i386/conf/Generic # # Generic -- Generic kernel configuration file for FreeBSD/i386 # Use this for multi-processor machines # include GENERIC ident Generic-GENERIC nodevice fwip # IP over FireWire (RFC 2734,3146) nodevice dcons # Dumb console driver nodevice dcons_crom # Configuration ROM for dcons - Peter From owner-freebsd-acpi@FreeBSD.ORG Tue Jun 5 19:22:55 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 9211A16A49E for ; Tue, 5 Jun 2007 19:22:55 +0000 (UTC) (envelope-from henrik@brixandersen.dk) Received: from solow.pil.dk (relay.pil.dk [195.41.47.164]) by mx1.freebsd.org (Postfix) with ESMTP id 5AA8513C44C for ; Tue, 5 Jun 2007 19:22:55 +0000 (UTC) (envelope-from henrik@brixandersen.dk) Received: from tirith.brixandersen.dk (osgiliath.brixandersen.dk [87.53.223.189]) by solow.pil.dk (Postfix) with ESMTP id 17EB61CC0F0 for ; Tue, 5 Jun 2007 21:22:54 +0200 (CEST) Received: by tirith.brixandersen.dk (Postfix, from userid 1001) id 86F8BBA52; Tue, 5 Jun 2007 21:22:53 +0200 (CEST) Date: Tue, 5 Jun 2007 21:22:53 +0200 From: Henrik Brix Andersen To: freebsd-acpi@freebsd.org Message-ID: <20070605192253.GE32418@tirith.brixandersen.dk> Mail-Followup-To: freebsd-acpi@freebsd.org References: <20070528180959.GA87728@tirith.brixandersen.dk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PPYy/fEw/8QCHSq3" Content-Disposition: inline In-Reply-To: <20070528180959.GA87728@tirith.brixandersen.dk> X-PGP-Key: http://www.brixandersen.dk/files/HenrikBrixAndersen.asc User-Agent: Mutt/1.5.15 (2007-04-06) Subject: Re: ACPI_FUNCTION_TRACE() and friends 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 19:22:55 -0000 --PPYy/fEw/8QCHSq3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 28, 2007 at 08:09:59PM +0200, Henrik Brix Andersen wrote: > How do I go about enabling output from the ACPI_FUNCTION_TRACE*() > macros as defined in src/sys/contrib/dev/acpica/acmacros.h? >=20 > I have added 'options ACPI_DEBUG' to my kernel configuration and tried > turning the debug sysctls all the way up: >=20 > # sysctl debug.acpi.layer=3D'ACPI_ALL_DRIVERS ACPI_ALL_COMPONENTS' > # sysctl debug.acpi.level=3D'ACPI_LV_VERBOSE' >=20 > Still, the ACPI_FUNCTION_TRACE_U32() macro does not produce any output > in dmesg. What did I miss here? Nobody knows the answer to this? :-( Regards, Brix --=20 Henrik Brix Andersen --PPYy/fEw/8QCHSq3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) Comment: GnuPG signed iD8DBQFGZbgMv+Q4flTiePgRAsk1AJ4xbc/p/L920XVaVlkIuyZO0sgH6QCgh9dh bCSgtiZX0yLLfhwCCAoQv5k= =JnRG -----END PGP SIGNATURE----- --PPYy/fEw/8QCHSq3-- From owner-freebsd-acpi@FreeBSD.ORG Tue Jun 5 19:26:57 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 27F2A16A46E for ; Tue, 5 Jun 2007 19:26:57 +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 A365813C468 for ; Tue, 5 Jun 2007 19:26:56 +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 l55JQqDB030227; Tue, 5 Jun 2007 15:26:54 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Peter Holm Date: Tue, 5 Jun 2007 15:26:47 -0400 User-Agent: KMail/1.9.6 References: <20070604183419.GA73268@peter.osted.lan> <46646BD3.5080900@root.org> <20070605043758.GA99622@peter.osted.lan> In-Reply-To: <20070605043758.GA99622@peter.osted.lan> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200706051526.48269.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 15:26:54 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/3362/Tue Jun 5 13:02:53 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 19:26:57 -0000 On Tuesday 05 June 2007 12:37:58 am Peter Holm wrote: > On Mon, Jun 04, 2007 at 12:45:23PM -0700, Nate Lawson wrote: > > 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. > > > > You are welcome :-) > > > 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 Is name a malloc'd variable? That might explain the low address. Perhaps we aren't properly respecting the top of high memory stuff from the BIOS when using SMAP? -- John Baldwin From owner-freebsd-acpi@FreeBSD.ORG Tue Jun 5 23:32:16 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 810CE16A469 for ; Tue, 5 Jun 2007 23:32:16 +0000 (UTC) (envelope-from jonathan@kc8onw.net) Received: from ms-smtp-04.nyroc.rr.com (ms-smtp-04.nyroc.rr.com [24.24.2.58]) by mx1.freebsd.org (Postfix) with ESMTP id 4BCC113C455 for ; Tue, 5 Jun 2007 23:32:16 +0000 (UTC) (envelope-from jonathan@kc8onw.net) Received: from mail.kc8onw.net (cpe-72-230-89-31.twcny.res.rr.com [72.230.89.31]) by ms-smtp-04.nyroc.rr.com (8.13.6/8.13.6) with ESMTP id l55NWE7x021194 for ; Tue, 5 Jun 2007 19:32:15 -0400 (EDT) Received: from www.kc8onw.net (localhost [127.0.0.1]) by mail.kc8onw.net (Postfix) with ESMTP id 75B422841F for ; Tue, 5 Jun 2007 19:32:14 -0400 (EDT) Received: from 69.61.188.89 (SquirrelMail authenticated user jonathan) by www.kc8onw.net with HTTP; Tue, 5 Jun 2007 19:32:14 -0400 (EDT) Message-ID: <56304.69.61.188.89.1181086334.squirrel@www.kc8onw.net> In-Reply-To: <200706051418.39948.jhb@freebsd.org> References: <62855.69.61.188.89.1180770401.squirrel@www.kc8onw.net> <200706051418.39948.jhb@freebsd.org> Date: Tue, 5 Jun 2007 19:32:14 -0400 (EDT) From: jonathan@kc8onw.net To: freebsd-acpi@freebsd.org User-Agent: SquirrelMail/1.5.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: Symantec AntiVirus Scan Engine Subject: Re: Unable to install System Control Interrupt handler [20070320] 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 23:32:16 -0000 On Tue, June 5, 2007 2:18 pm, John Baldwin wrote: > On Saturday 02 June 2007 03:46:41 am jonathan@kc8onw.net wrote: > >> I just updated to the latest -current from 6.2 release on an amd64 >> system and get the below error ACPI Exception (evevent-0257): >> AE_ALREADY_EXISTS, Unable to install System >> Control Interrupt handler [20070320] >> >> >> I found this thread that discusses it as well but it seems to have >> mostly died off without a clear resolution. >> > http://lists.freebsd.org/mailman/htdig/freebsd-acpi/2005-December/002307. > html >> >> I know the BIOS in this machine is pretty poor but I would like to get >> it working. > > Add 'device atpic' to your kernel. That fixed it! Thank you very much, Jonathan From owner-freebsd-acpi@FreeBSD.ORG Wed Jun 6 16:47:30 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 2692A16A46B for ; Wed, 6 Jun 2007 16:47:30 +0000 (UTC) (envelope-from zflyer@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.232]) by mx1.freebsd.org (Postfix) with ESMTP id DB4B513C4BB for ; Wed, 6 Jun 2007 16:47:29 +0000 (UTC) (envelope-from zflyer@gmail.com) Received: by wx-out-0506.google.com with SMTP id h28so177378wxd for ; Wed, 06 Jun 2007 09:47:29 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=NdycRN27rlzQIFRoo3EFhGciz23oX0L5xpo0QFTH4pOP8FvRY7ECiz5ro4yEk/88oEKC2ZfGhkw8bmbYWipGp0Lusbl1O1HrlqMTrVt0MJaYZ3U/Xj6RpQTR6G7mWvGkJSEBvpy+pqNvWiWaEC2qE2Kgw8Bi5+Tze3pLhCrSj6U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=CJ+p103m6xpVrHBI3yiOBoPw7RxjhfivA6y+TcMlW1y6SZRJA2TWp78YrL8Cl18d+WJ6+ao6DG8uWiupvlL4mfdtqPN18s8QHk4GGB85NGkjqqG9C7XG1qwO6z2wyI7+V8jh/+vwA+eJO+5YuLUR4kfMyVV4y+MlXwwriuyZ7EY= Received: by 10.70.87.9 with SMTP id k9mr1092816wxb.1181146967696; Wed, 06 Jun 2007 09:22:47 -0700 (PDT) Received: by 10.70.20.2 with HTTP; Wed, 6 Jun 2007 09:22:47 -0700 (PDT) Message-ID: <6293ba970706060922h756fd7el1d3d54b2c1c44bc3@mail.gmail.com> Date: Wed, 6 Jun 2007 12:22:47 -0400 From: Steve To: freebsd-acpi@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Wake-on-LAN questions 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, 06 Jun 2007 16:47:30 -0000 Hello, I have two 6.2 PCs and have had no luck getting WOL working on either. Both PCs have WOL/PME enabled in BIOS, an Intel Pro/1000 and Pro/100 NIC. Neither has any link light after a shutdown (S5). Is there a ACPI setting that I'm missing that keeps the NICs powered and able to receive a WOL packet? Any way to diagnose this issue or other sysctl knobs to try? Thanks for any help. S.