From owner-freebsd-current@FreeBSD.ORG Mon Jan 23 21:34:13 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB95C16A51F for ; Mon, 23 Jan 2006 21:34:04 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F46C4459F for ; Mon, 23 Jan 2006 21:16:58 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (9en8hf0ps675kpep@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.3/8.13.3) with ESMTP id k0NLFuOQ075777; Mon, 23 Jan 2006 13:15:56 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.3/8.13.3/Submit) id k0NLFtOl075776; Mon, 23 Jan 2006 13:15:55 -0800 (PST) (envelope-from jmg) Date: Mon, 23 Jan 2006 13:15:55 -0800 From: John-Mark Gurney To: Alex Burke Message-ID: <20060123211555.GA69162@funkthat.com> Mail-Followup-To: Alex Burke , FreeBSD CURRENT References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: FreeBSD CURRENT Subject: Re: Swap_pager and modified after free console messages X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jan 2006 21:34:13 -0000 Alex Burke wrote this message on Mon, Jan 23, 2006 at 19:14 +0000: > This is what I have seen over the past few days: > 1) kernel: memoery modified after free and then what appears to be a > memory address complete kernel message is necessary... there is other info than just kernel address in that message... > I saw another post mentioning a console message like this that > appeared to be related to the subsequent panic, but mine hasnt caused > the machine to panic. I am not sure if this is because I have the > standard -CURRENT GENERIC kernel running (with WITNESS, INVARIANTS > still enabled), but a reply said use memgaurd to track down the issue. > How should I configure this? memguard(9) -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."