Date: Wed, 13 Oct 2010 15:14:57 +0200 From: Hans Petter Selasky <hselasky@c2i.net> To: Andriy Gapon <avg@icyb.net.ua> Cc: freebsd-acpi@freebsd.org Subject: Re: MacBookPro 5,1 Message-ID: <201010131514.57188.hselasky@c2i.net> In-Reply-To: <4CB4C882.6050006@icyb.net.ua> References: <201010121209.06397.hselasky@c2i.net> <201010121425.07279.hselasky@c2i.net> <4CB4C882.6050006@icyb.net.ua>
index | next in thread | previous in thread | raw e-mail
On Tuesday 12 October 2010 22:43:46 Andriy Gapon wrote:
> on 12/10/2010 15:25 Hans Petter Selasky said the following:
> > On Tuesday 12 October 2010 13:15:26 Andriy Gapon wrote:
> >> on 12/10/2010 13:09 Hans Petter Selasky said the following:
> >>> Hi,
> >>>
> >>> My MacBookPro 5,1 does not boot using -current because memory inside
> >>> the ACPI kernel module is used after free.
> >>>
> >>> The following patch temporily mitigates the problem:
> >>>
> >>> /usr/src/sys/dev/acpica/Osd/OsdMemory.c
> >>>
> >>> void
> >>> AcpiOsFree(void *Memory)
> >>> {
> >>> + if (cold == 0)
> >>>
> >>> free(Memory, M_ACPICA);
> >>>
> >>> }
> >>>
> >>> Is there any way to debug this from user-land?
> >>
> >> I think that the best way is to get a backtrace at least or better a
> >> crashdump.
> >
> > The crashdump is not helpful. It crashes at init time, while the actual
> > free happens very early during boot.
>
> Still a backtrace would be useful, I think.
> Or track all calls to AcpiOsFree, e.g. using DTrace or stack(9) or etc.
Do you have any hints how a shall configure DTrace to trace AcpiOsFree() ?
--HPS
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201010131514.57188.hselasky>