From owner-freebsd-acpi@FreeBSD.ORG  Thu Nov  3 01:49:03 2005
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
X-Original-To: freebsd-acpi@freebsd.org
Delivered-To: freebsd-acpi@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 3EB2716A41F;
	Thu,  3 Nov 2005 01:49:03 +0000 (GMT)
	(envelope-from keramida@ceid.upatras.gr)
Received: from kane.otenet.gr (kane.otenet.gr [195.170.0.95])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6D2F043D45;
	Thu,  3 Nov 2005 01:49:01 +0000 (GMT)
	(envelope-from keramida@ceid.upatras.gr)
Received: from flame.pc (patr530-a063.otenet.gr [212.205.215.63])
	by kane.otenet.gr (8.13.4/8.13.4/Debian-1) with ESMTP id jA31mwNf025773;
	Thu, 3 Nov 2005 03:48:59 +0200
Received: from flame.pc (flame [127.0.0.1])
	by flame.pc (8.13.4/8.13.4) with ESMTP id jA31mpFD001646;
	Thu, 3 Nov 2005 03:48:51 +0200 (EET)
	(envelope-from keramida@ceid.upatras.gr)
Received: (from keramida@localhost)
	by flame.pc (8.13.4/8.13.4/Submit) id jA31lec1001629;
	Thu, 3 Nov 2005 03:47:40 +0200 (EET)
	(envelope-from keramida@ceid.upatras.gr)
Date: Thu, 3 Nov 2005 03:47:40 +0200
From: Giorgos Keramidas <keramida@ceid.upatras.gr>
To: Nate Lawson <nate@root.org>
Message-ID: <20051103014740.GA1586@flame.pc>
References: <971FCB6690CD0E4898387DBF7552B90E0346CAFB@orsmsx403.amr.corp.intel.com>
	<20051103.094643.74756456.haro@h4.dion.ne.jp>
	<436961FD.3040605@root.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <436961FD.3040605@root.org>
Cc: freebsd-acpi@freebsd.org, freebsd-current@freebsd.org,
	robert.moore@intel.com, jkim@freebsd.org
Subject: Re: Panic on boot with new ACPI-CA
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: Thu, 03 Nov 2005 01:49:03 -0000

On 2005-11-02 17:03, Nate Lawson <nate@root.org> wrote:
> As I mentioned to Jung-uk, the problem is likely an error in
> acpi-ca modifying memory after it has freed it.  The way to
> track this down is to enable memguard(9).  See the man page for
> info.  You need to add options DEBUG_MEMGUARD to your kernel,
> set the malloc type to watch to M_ACPICA, and rebuild your
> kernel and modules.  Memguard sets page permissions so we can
> catch the culprit who is modifying the memory.

This is exactly the messgae printed on my console at panic time
-- of memory modified after free.  I'm building a kernel with
MEMGUARD now, but it's probably going to be a bit hard to get a
kernel dump, because the panic happens before disks are available
and I don't have a serial console here.