From owner-acpi-jp@jp.FreeBSD.org Tue Dec 11 03:35:38 2001
Received: (from daemon@localhost)
	by castle2.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) id fBAIZc697523;
	Tue, 11 Dec 2001 03:35:38 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from castle.jp.freebsd.org (castle.jp.FreeBSD.org [210.226.20.15])
	by castle2.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) with ESMTP/inet id fBAIZbm97518
	for <acpi-jp@castle2.jp.freebsd.org>; Tue, 11 Dec 2001 03:35:37 +0900 (JST)
	(envelope-from iwasaki@jp.freebsd.org)
Received: from tasogare.imasy.or.jp (root@tasogare.imasy.or.jp [202.227.24.5])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id DAA23682
	for <acpi-jp@jp.FreeBSD.org>; Tue, 11 Dec 2001 03:35:37 +0900 (JST)
	(envelope-from iwasaki@jp.FreeBSD.org)
Received: from localhost (root@localhost [127.0.0.1])
	(authenticated as iwa with CRAM-MD5)
	by tasogare.imasy.or.jp (8.11.6+3.4W/8.11.6/tasogare) with ESMTP/inet id fBAIZZP96160;
	Tue, 11 Dec 2001 03:35:35 +0900 (JST)
	(envelope-from iwasaki@jp.FreeBSD.org)
Date: Tue, 11 Dec 2001 03:35:31 +0900 (JST)
Message-Id: <20011211.033531.57437214.iwasaki@jp.FreeBSD.org>
To: acpi-jp@jp.FreeBSD.org, mb@imp.ch
From: Mitsuru IWASAKI <iwasaki@jp.FreeBSD.org>
In-Reply-To: <20011210182130.M16571-100000@levais.imp.ch>
References: <20011211.015717.59648402.iwasaki@jp.FreeBSD.org>
	<20011210182130.M16571-100000@levais.imp.ch>
X-Mailer: Mew version 2.0 on Emacs 20.7 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: acpi-jp@jp.FreeBSD.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+010331
X-Sequence: acpi-jp 1533
Subject: [acpi-jp 1533] Re: acpi broken with new siemens amilo 1.0
 notebook (DSDT is corrupt)
Errors-To: owner-acpi-jp@jp.FreeBSD.org
Sender: owner-acpi-jp@jp.FreeBSD.org
X-Originator: iwasaki@jp.FreeBSD.org

Hi,

> > How about adding ACPI_DEBUG=yes to your /etc/make.conf and
> > debug.acpi.layer="ACPI_ALL_COMPONENTS", debug.acpi.level="ACPI_LV_ERROR"
> > to your /boot/loader.conf ?
> 
> I did this, but get not more detailed output. Where should I
> get this output ?

Hmmm, do you compile acpi in your kernel?  If so, just add
options ACPI_DEBUG in your kernel config too.
Most of ACPICA errors display thier reason, for example,
files contains AE_AML_OPERAND_TYPE are;
% grep AE_AML_OPERAND_TYPE *.c | sed 's/:.*//' | uniq
dsopcode.c
dswexec.c
dswload.c
exfield.c
exfldio.c
exoparg1.c
exoparg2.c
exprep.c
exresnte.c
exresop.c
exstore.c
exstoren.c
rsutils.c

and typical error printing like this;
% grep -5 AE_AML_OPERAND_TYPE dsopcode.c
    if (ACPI_GET_DESCRIPTOR_TYPE (ResDesc) != ACPI_DESC_TYPE_NAMED)
    {
        ACPI_DEBUG_PRINT ((ACPI_DB_ERROR, "(%s) destination must be a NS Node\n",
            AcpiPsGetOpcodeName (Op->Opcode)));

        Status = AE_AML_OPERAND_TYPE;
        goto Cleanup;
    }

    /*
     * Setup the Bit offsets and counts, according to the opcode
--

you can add printf lines just before AE_AML_OPERAND_TYPE in the files
which have no error printings and figure out where the error occurs.

Thanks
