From owner-freebsd-acpi@FreeBSD.ORG  Mon Mar 27 09:23:30 2006
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
X-Original-To: freebsd-acpi@freebsd.org
Delivered-To: freebsd-acpi@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4FE0116A400;
	Mon, 27 Mar 2006 09:23:30 +0000 (UTC)
	(envelope-from fukui.FreeBSD@fanet.net)
Received: from mail.fanet.net (home.fanet.net [61.194.26.34])
	by mx1.FreeBSD.org (Postfix) with ESMTP id B331243D45;
	Mon, 27 Mar 2006 09:23:29 +0000 (GMT)
	(envelope-from fukui.FreeBSD@fanet.net)
Received: from mail.fanet.net (user=fukui mech=CRAM-MD5 bits=0)
	by mail.fanet.net (8.13.5+3.5Wbeta/8.13.5/smtpfeed 1.20) with ESMTP id
	k2R9NLkc006111; Mon, 27 Mar 2006 18:23:24 +0900 (JST)
	(envelope-from fukui.FreeBSD@fanet.net)
Date: Mon, 27 Mar 2006 18:23:21 +0900
Message-ID: <ulkuw44xi.wl@mail.fanet.net>
From: Masayuki FUKUI <fukui.FreeBSD@fanet.net>
To: nate@root.org
In-Reply-To: <44206C20.1060603@root.org>
References: <200603210033.k2L0Xorb043252@freefall.freebsd.org>
	<200603211343.55664.jhb@freebsd.org> <442060E8.2000908@root.org>
	<44206C20.1060603@root.org>
User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.6
	(=?ISO-2022-JP?B?GyRCNF0yLBsoQg==?=) LIMIT/1.14.9
	(=?ISO-2022-JP?B?GyRCRjtMQDt7GyhC?=) APEL/10.6 Emacs/21.4
	(i386-mingw-nt5.1.2600) MULE/5.0 (=?ISO-2022-JP?B?GyRCOC1MWhsoQg==?=)
	Meadow/2.10 (ASAGAO)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - =?ISO-2022-JP?B?IhskQjRdGyhC?=
	=?ISO-2022-JP?B?GyRCMiwbKEIi?=)
Content-Type: text/plain; charset=US-ASCII
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,UNPARSEABLE_RELAY 
	autolearn=ham version=3.1.0
X-Spam-Checker-Version: SpamAssassin 3.1.0
Cc: freebsd-acpi@freebsd.org, bug-followup@freebsd.org
Subject: Re: i386/93963: [panic] [patch] ACPI Panic with some ACPI 2.0 PC
	&	cannot boot
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: Mon, 27 Mar 2006 09:23:30 -0000

>>>>> In <44206C20.1060603@root.org> 
>>>>>	Nate Lawson <nate@root.org> wrote:
> I contacted Robert Moore at Intel and he informed us this is fixed in 
> the 200506 distro of acpi-ca.  We have an even newer version in 
> 7-current, so you can test that also to be sure it fixes your problem.

Thank you, Nate-san.
I tested it, and 7-current (7.0-CURRENT-SNAP013-i386) could be booted.

> Unfortunately, we cannot MFC acpi-ca to 6.x until a known memory leak is 
> fixed.  We'll close this bug once 7-current works for you and we are 
> able to MFC acpi-ca.

I see.

PS
`acpidump -t' terminates abnormally.

|# acpidump -t
|/*
|  RSD PTR: OEM=PTLTD, ACPI_Rev=2.0x (2)
|        XSDT=0x00000000, length=0, cksum=0
| */
|acpidump: can't map address: Invalid argument