From owner-freebsd-acpi@FreeBSD.ORG Tue Sep 21 09:04:55 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 A7EC4106566C; Tue, 21 Sep 2010 09:04:55 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 9EE038FC12; Tue, 21 Sep 2010 09:04:54 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id MAA00459; Tue, 21 Sep 2010 12:04:42 +0300 (EEST) (envelope-from avg@icyb.net.ua) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1OxymI-000Nv6-CU; Tue, 21 Sep 2010 12:04:42 +0300 Message-ID: <4C987529.30300@icyb.net.ua> Date: Tue, 21 Sep 2010 12:04:41 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.9) Gecko/20100918 Lightning/1.0b2 Thunderbird/3.1.4 MIME-Version: 1.0 To: Ian Smith References: <20100921001533.803ef029.daniel.bilik@neosystem.cz> <4C9858E2.4060602@icyb.net.ua> <20100921182057.B11124@sola.nimnet.asn.au> In-Reply-To: <20100921182057.B11124@sola.nimnet.asn.au> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Daniel Bilik , freebsd-acpi@freebsd.org 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:04:55 -0000 on 21/09/2010 11:41 Ian Smith said the following: > 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 This check and message should be abolished altogether, I thought that mav was going to do that. As Daniel correctly said, this has nothing to do with acpi attach failing and the system would be useless without it. Perhaps, the above message is even a result of acpi failure, but that's irrelevant. -- Andriy Gapon