MacBookPro 5,1

Hans Petter Selasky hselasky at c2i.net
Wed Oct 20 07:49:41 UTC 2010


On Wednesday 20 October 2010 08:55:09 Andriy Gapon wrote:
> on 20/10/2010 09:34 Hans Petter Selasky said the following:
> > 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:
> > 
> > pcib0: <ACPI Host-PCI bridge> on acpi0
> > pci0: <ACPI PCI bus> on pcib0
> > pci_link32: Enter debugger
> > 
> > **** Context Switch from TID 0xffffffffffffffff to TID 0x186a0 ****
> > 
> >   rscalc-0293 [0x186a0] [188762] RsGetAmlLength        : ----Entry
> >   rscalc-0369 [0x186a0] [188762] RsGetAmlLength        : ----Exit- AE_OK
> >   rslist-0225 [0x186a0] [188762] RsConvertResourcesToAm: ----Entry
> >   rsmisc-0437 [0x186a0] [188763] RsConvertResourceToAml: ----Entry
> >   rsmisc-0636 [0x186a0] [188763] RsConvertResourceToAml: ----Exit- AE_OK
> >   rsmisc-0437 [0x186a0] [188763] RsConvertResourceToAml: ----Entry
> >   rsmisc-0636 [0x186a0] [188763] RsConvertResourceToAml: ----Exit- AE_OK
> >   rslist-0273 [0x186a0] [188762] RsConvertResourcesToAm: ----Exit- AE_OK
> > 
> > rscreate-0554 [0x186a0] [188761] RsCreateAmlResources  : OutputBuffer
> > 0xffffff00031f9000 Length D
> > Dirty free 0xffffff00031f9000 13 at 13
> > KDB: stack backtrace:
> > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a
> > AcpiOsFree() at AcpiOsFree+0x72
> > AcpiUtDeleteInternalObj() at AcpiUtDeleteInternalObj+0x335
> > AcpiUtUpdateRefCount() at AcpiUtUpdateRefCount+0x188
> > AcpiUtUpdateObjectReference() at AcpiUtUpdateObjectReference+0x6e
> > AcpiUtRemoveReference() at AcpiUtRemoveReference+0xd5
> > AcpiRsSetSrsMethodData() at AcpiRsSetSrsMethodData+0x14b
> > AcpiSetCurrentResources() at AcpiSetCurrentResources+0xb8
> > acpi_pci_link_route_irqs() at acpi_pci_link_route_irqs+0x204
> 
> Can you please check which branch is executed here?
> if (sc->pl_crs_bad)
>         status = acpi_pci_link_srs_from_links(sc, &srsbuf);
> else
>         status = acpi_pci_link_srs_from_crs(sc, &srsbuf);

The not bad case.

--HPS


More information about the freebsd-acpi mailing list