From owner-acpi-jp@jp.freebsd.org  Tue Oct  2 17:15:43 2001
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id RAA32632;
	Tue, 2 Oct 2001 17:15:43 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id RAA32611;
	Tue, 2 Oct 2001 17:15:36 +0900 (JST)
	(envelope-from max@vega.com)
Received: from vega.vega.com (h178.229.dialup.iptcom.net [212.9.229.178])
	by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id LAA77243;
	Tue, 2 Oct 2001 11:14:49 +0300 (EEST)
	(envelope-from max@vega.com)
Received: (from max@localhost)
	by vega.vega.com (8.11.6/8.11.3) id f928EHV73680;
	Tue, 2 Oct 2001 11:14:17 +0300 (EEST)
	(envelope-from sobomax@FreeBSD.org)
From: Maxim Sobolev <sobomax@FreeBSD.ORG>
Message-Id: <200110020814.f928EHV73680@vega.vega.com>
To: iwasaki@jp.FreeBSD.org (Mitsuru IWASAKI)
Date: Tue, 2 Oct 2001 11:13:37 +0300 (EEST)
Cc: sobomax@FreeBSD.ORG, ache@nagual.pp.ru, msmith@FreeBSD.ORG,
        current@FreeBSD.ORG, acpi-jp@jp.FreeBSD.org
In-Reply-To: <no.id> from "Mitsuru IWASAKI" at Oct 02, 2001 11:10:45 AM
X-Mailer: ELM [version 2.5 PL5]
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+010328
X-Sequence: acpi-jp 1316
Subject: [acpi-jp 1316] Re: ACPI: problem with fdc resource allocation
Errors-To: owner-acpi-jp@jp.freebsd.org
Sender: owner-acpi-jp@jp.freebsd.org
X-Originator: sobomax@FreeBSD.ORG

> 
> Hi, I've just made a workaround for this.  Intel folks, could you review
> it as always?
> 
> > The problem is here, right?
> > > can't fetch resources for \\_SB_.PCI0.ISA_.FDC0 - AE_AML_BUFFER_LIMIT
> > 
> > I'm sure _SB_.PCI0.ISA_.FDC0._CRS (Current Resource Settings) have some
> > problems (not sure in BIOS or ACPICA yet).  I could reproduce the problem
> > which you reported.  Trace attached in this mail.
> [snip]
> > dsopcode-0677 [09] DsEvalBufferFieldOpera: Field size 208 exceeds Buffer size 192 (bits)
> > PsExecute: method failed - \_SB_.PCI0.ISA_.FDC0._CRS (0x8098fa8)
> > Execution of \_SB_.PCI0.ISA_.FDC0._CRS failed with status AE_AML_BUFFER_LIMIT
> 
> This method is like this;
>                 Method(_CRS) {
>                     Name(BUF0, Buffer(0x18) {0x47, 0x1, 0xf2, 0x3, 0xf2, 0x3,
> 			       0x0, 0x4, 0x47, 0x1, 0xf7, 0x3, 0xf7, 0x3, 0x0,
> 			       0x1, 0x22, 0x40, 0x0, 0x2a, 0x4, 0x0, 0x79, 0x0 })
>                     CreateByteField(BUF0, 0x2, IOLO)
>                     CreateByteField(BUF0, 0x3, IOHI)
>                     CreateByteField(BUF0, 0x4, IORL)
>                     CreateByteField(BUF0, 0x5, IORH)
>                     CreateByteField(BUF0, 0x19, IRQL)
>                     CreateByteField(BUF0, 0x1c, DMAV)
>                     Return(BUF0)
>                 }
> 
> The problem is that this AML is trying to create a field at exceeded
> position (0x19) of the Buffer (size is 0x18).
> I couldn't find how AML interprepter treat this in ACPI Spec. so I'm
> not sure wether AWRDACPI violates the Spec. or ACPICA can have a workaround
> for this.
> Anyway, I made a patch to reallocate a large enough buffer for the
> requested operation.

Yes, that patch fixed the problem, thank you!

-Maxim
