From owner-freebsd-acpi@FreeBSD.ORG  Fri Nov  5 20:26:35 2010
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
Delivered-To: freebsd-acpi@FreeBSD.org
Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28])
	by hub.freebsd.org (Postfix) with ESMTP id 3D4581065673;
	Fri,  5 Nov 2010 20:26:34 +0000 (UTC)
	(envelope-from jkim@FreeBSD.org)
From: Jung-uk Kim <jkim@FreeBSD.org>
To: freebsd-acpi@FreeBSD.org
Date: Fri, 5 Nov 2010 16:26:19 -0400
User-Agent: KMail/1.6.2
References: <201010121209.06397.hselasky@c2i.net>
	<201011051615.24705.jkim@FreeBSD.org>
In-Reply-To: <201011051615.24705.jkim@FreeBSD.org>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201011051626.26913.jkim@FreeBSD.org>
Cc: "Moore, Robert" <robert.moore@intel.com>, jhb@FreeBSD.org, avg@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 <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
	<mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
	<mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Nov 2010 20:26:35 -0000

On Friday 05 November 2010 04:14 pm, Jung-uk Kim wrote:
> On Tuesday 12 October 2010 06:09 am, Hans Petter Selasky wrote:
> > 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?
>
> FYI, this problem should be fixed in r214848.

And r214849.  I forgot to change one line. :-(

Sorry,

Jung-uk Kim