From owner-freebsd-acpi@FreeBSD.ORG Tue Sep 21 09:58:22 2010 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C33F61065670 for ; Tue, 21 Sep 2010 09:58:22 +0000 (UTC) (envelope-from daniel.bilik@neosystem.cz) Received: from mx.neosystem.cz (mx.neosystem.cz [IPv6:2002:5856:6e27:15::10]) by mx1.freebsd.org (Postfix) with ESMTP id 808EA8FC12 for ; Tue, 21 Sep 2010 09:58:22 +0000 (UTC) Received: from tao.neosystem.cz (localhost [127.0.0.1]) by mx.neosystem.cz (Postfix) with ESMTP id CD41730DB; Tue, 21 Sep 2010 11:58:21 +0200 (CEST) X-Virus-Scanned: amavisd-new at mx.neosystem.cz Received: from neon.sn.neosystem.cz (unknown [172.19.40.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.neosystem.cz (Postfix) with ESMTPSA id 8AEA33024; Tue, 21 Sep 2010 11:58:11 +0200 (CEST) Date: Tue, 21 Sep 2010 11:53:25 +0200 From: Daniel Bilik To: freebsd-acpi@freebsd.org Message-Id: <20100921115325.7f4c7ecd.daniel.bilik@neosystem.cz> In-Reply-To: <20100921182057.B11124@sola.nimnet.asn.au> References: <20100921001533.803ef029.daniel.bilik@neosystem.cz> <4C9858E2.4060602@icyb.net.ua> <20100921182057.B11124@sola.nimnet.asn.au> Organization: neosystem.cz X-Mailer: Sylpheed 3.0.3 (GTK+ 2.20.1; amd64-portbld-freebsd8.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Ian Smith Subject: Re: acpi0: Could not initialise SystemMemory handler: AE_NOT_EXIST 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, 21 Sep 2010 09:58:22 -0000 On Tue, 21 Sep 2010 18:41:45 +1000 (EST) Ian Smith wrote: > I don't know anything about that, but having looked over our RTC code > lately re another issue, I also wonder about the significance of this: > > RTC BIOS diagnostic error 96 > ... > Daniel: have there been any other RTC messages like that along the way? > Perhaps seeing all of your dmesg might shine some more light? There are no failures or warnings reported by BIOS during boot, and settings were changed (and saved) there several times during my tests. Also there is no such "diagnostic error" in Linux dmesg, so I think Andriy is right here, ie. this may be a result of failed acpi attach, but not a source of it. Complete (well, almost, as I was not quick enough to take a picture of the screen with CPU identification :)) dmesg follows: --- Copyright (c) 1992-2010 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.1-RELEASE #0: Mon Jul 19 02:36:49 UTC 2010 root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 ... TSC: P-state invariant real memory = 2147483648 (2048 MB) avail memory = 2037829632 (1943 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUS FreeBSD/SMP: 1 package(s) x 1 core(s) x 2 HTT threads cpu0 (BSP): APIC ID: 0 cpu1 (AP/HT): APIC ID: 1 ioapic0: Changing APIC ID to 1 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard ACPI Error: No handler for Region [PMIO] (0xffffff00024b1d00) [SystemIO] (20100331/evregion-487) ACPI Error: Region SystemIO(0x1) has no handler (20100331/exfldio-383) ACPI Error (psparse-0633): Method parse/execution failed [\_SB_.PCI0.GSWS] (Node 0xffffff00024c63e0), AE_NOT_EXIST ACPI Error (psparse-0633): Method parse/execution failed [\_SB_.SSMI] (Node 0xffffff00024af400), AE_NOT_EXIST ACPI Error (psparse-0633): Method parse/execution failed [\_SB_.PCI0.GFX0._REG] (Node 0xffffff00024ac9e0), AE_NOT_EXIST acpi0: Could not initialise SystemMemory handler: AE_NOT_EXIST device_attach: acpi0 attach returned 6 RTC BIOS diagnostic error 96 Timecounters tick every 1.000 msec md0: Preloaded image 4194304 bytes at 0xffffffff80e6aa98 SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/md0 warning: no time-of-day clock registered, system time will not be set accurately --- Thank you for looking at this. -- Daniel Bilik