From owner-freebsd-acpi@FreeBSD.ORG  Tue Sep 21 11:09:59 2010
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
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 80B131065670
	for <freebsd-acpi@freebsd.org>; Tue, 21 Sep 2010 11:09:59 +0000 (UTC)
	(envelope-from smithi@nimnet.asn.au)
Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159])
	by mx1.freebsd.org (Postfix) with ESMTP id EBC9C8FC08
	for <freebsd-acpi@freebsd.org>; Tue, 21 Sep 2010 11:09:58 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
	by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id o8LB9tgC031731;
	Tue, 21 Sep 2010 21:09:56 +1000 (EST)
	(envelope-from smithi@nimnet.asn.au)
Date: Tue, 21 Sep 2010 21:09:55 +1000 (EST)
From: Ian Smith <smithi@nimnet.asn.au>
To: Andriy Gapon <avg@icyb.net.ua>
In-Reply-To: <4C987529.30300@icyb.net.ua>
Message-ID: <20100921203307.Y11124@sola.nimnet.asn.au>
References: <20100921001533.803ef029.daniel.bilik@neosystem.cz>
	<4C9858E2.4060602@icyb.net.ua>
	<20100921182057.B11124@sola.nimnet.asn.au>
	<4C987529.30300@icyb.net.ua>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: Daniel Bilik <daniel.bilik@neosystem.cz>, 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 <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
	<mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
	<mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Sep 2010 11:09:59 -0000

On Tue, 21 Sep 2010, Andriy Gapon wrote:
 > 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<clock_battery,memory_size,invalid_time>
 > 
 > This check and message should be abolished altogether, I thought that mav was
 > going to do that.

Oh, ok.  The MC146818 doesn't even have a register E, and we check 
register D for RTCSD_PWR on a read anyway, so 0x0e is just RAM, and 
finding any bits set there makes atrtc_setup_clock fail - as it did!

 > 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.

I doubt the former, but the latter is true :)  I was reading isa/atrtc.c 
to a) try working out how to do the wakeup-on-timer thing and b) tracing 
ct_to_ts and ts_to_ct messages re another problem - both other topics.

sorry, Ian