on 13/10/2010 16:14 Hans Petter Selasky said the following: > 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.
So no backtrace yet? :-) >> 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() ? You set up DTrace using general procedure: http://wiki.freebsd.org/DTrace The you can write a little DTrace script to trace calls to AcpiOsFree (and perhaps/probably AcpiOsAllocate) using fbt provider: http://wikis.sun.com/display/DTrace/fbt+Provider Sorry, EBUSY to write a complete script right now. You might find DTrace function stack() and aggregations useful. Things are bit trickier if the crash happens before you have a chance to do anything in userland. -- Andriy Gapon _______________________________________________ freebsd-acpi@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-acpi To unsubscribe, send any mail to "freebsd-acpi-unsubscr...@freebsd.org"