MacBookPro 5,1

[Lin Ming]

On Wed, 2010-10-20 at 16:06 +0800, Hans Petter Selasky wrote:
> On Wednesday 20 October 2010 08:36:31 Lin Ming wrote:
> > On Wed, 2010-10-20 at 14:34 +0800, Hans Petter Selasky wrote:
> > > On Tuesday 19 October 2010 07:47:02 Lin Ming wrote:
> > > > On Tue, 2010-10-19 at 04:21 +0800, Hans Petter Selasky wrote:
> > > > > On Monday 18 October 2010 02:01:09 Moore, Robert wrote:
> > > > > > Can you send us the acpidump for the machine?
> > > > > > 
> > > > > > Also, tell us which control method is failing.
> > > > > > 
> > > > > > Thanks
> > > > > 
> > > > > Hi,
> > > > > 
> > > > > Please find attached dump of ACPI tables.
> > > > > 
> > > > > It is the function AcpiRsCreateAmlResources() which writes beyond the
> > > > > buffer it allocates.
> > > > 
> > > > Could you enable AML debug output to get more info?
> > > > But I don't know how to enable it on FreeBSD.
> > > > 
> > > > In Linux, the AML debug output is enabled with kernel boot parameters
> > > > like below.
> > > > acpi.debug_layer=0xffffffff acpi.debug_level=0xffffffff
> > > > 
> > > > FreeBSD may have some similar boot parameters.
> > > 
> > > I've enabled the debug prints just around the failing function. Here is
> > > the
> > 
> > > result:
> > What's the kernel parameters are you using?
> > There should be a lot of AML debug output.
> 
> 
> Hi,
> 
> During the function call that overwrites it's buffer, there are no more debug 
> prints than shown in the code, even with all debug prints on. Where should I 
> add more debug prints?

I'm trying to reproduce this bug in the acpi simulator(acpiexec).
Will get back to you.

Lin Ming