From owner-freebsd-acpi@FreeBSD.ORG Tue Oct 12 11:15:32 2010 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9A24E106564A for ; Tue, 12 Oct 2010 11:15:32 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id E2F318FC16 for ; Tue, 12 Oct 2010 11:15:31 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id OAA16397; Tue, 12 Oct 2010 14:15:27 +0300 (EEST) (envelope-from avg@icyb.net.ua) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1P5cpL-000OOz-4I; Tue, 12 Oct 2010 14:15:27 +0300 Message-ID: <4CB4434E.7020006@icyb.net.ua> Date: Tue, 12 Oct 2010 14:15:26 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.9) Gecko/20100918 Lightning/1.0b2 Thunderbird/3.1.4 MIME-Version: 1.0 To: Hans Petter Selasky References: <201010121209.06397.hselasky@c2i.net> In-Reply-To: <201010121209.06397.hselasky@c2i.net> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org Subject: Re: MacBookPro 5,1 X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Oct 2010 11:15:32 -0000 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. -- Andriy Gapon