From owner-freebsd-acpi@FreeBSD.ORG Thu Nov 3 14:25:02 2005 Return-Path: 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 A0CEC16A421; Thu, 3 Nov 2005 14:25:02 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from rosebud.otenet.gr (rosebud.otenet.gr [195.170.0.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4064243D6E; Thu, 3 Nov 2005 14:25:00 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from flame.pc (aris.bedc.ondsl.gr [62.103.39.226]) by rosebud.otenet.gr (8.13.4/8.13.4/Debian-1) with SMTP id jA3EOrD9031590; Thu, 3 Nov 2005 16:24:58 +0200 Received: from flame.pc (flame [127.0.0.1]) by flame.pc (8.13.4/8.13.4) with ESMTP id jA3EOlFV001833; Thu, 3 Nov 2005 16:24:47 +0200 (EET) (envelope-from keramida@freebsd.org) Received: (from keramida@localhost) by flame.pc (8.13.4/8.13.4/Submit) id jA3EOkcl001832; Thu, 3 Nov 2005 16:24:46 +0200 (EET) (envelope-from keramida@freebsd.org) Date: Thu, 3 Nov 2005 16:24:46 +0200 From: Giorgos Keramidas To: Nate Lawson Message-ID: <20051103142446.GA1787@flame.pc> References: <971FCB6690CD0E4898387DBF7552B90E0346CAFB@orsmsx403.amr.corp.intel.com> <20051103.094643.74756456.haro@h4.dion.ne.jp> <436961FD.3040605@root.org> <20051103014740.GA1586@flame.pc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051103014740.GA1586@flame.pc> 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 14:25:02 -0000 On 2005-11-03 03:47, Giorgos Keramidas wrote: >On 2005-11-02 17:03, Nate Lawson 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. This is definitely something that is ACPI-related. I updated my sources to the last commit before the start of the ACPI import: build@flame:/home/build/src$ cvs -qR up -APd -D '2005/11/01 22:00:00 UTC' Rebuilt everything and I see no panics now. I'll use the watchpoint trick Nate posted when I have a new build to test. - Giorgos