>
> 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
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
