From owner-freebsd-bugs@FreeBSD.ORG Fri May 27 11:22:26 2011 Return-Path: Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 88AC5106566B; Fri, 27 May 2011 11:22:26 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.64.117]) by mx1.freebsd.org (Postfix) with ESMTP id 0C6F58FC13; Fri, 27 May 2011 11:22:25 +0000 (UTC) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.14.4/8.14.4) with ESMTP id p4RBMOeo099988; Fri, 27 May 2011 15:22:24 +0400 (MSD) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.14.4/8.14.4/Submit) id p4RBMO6w099987; Fri, 27 May 2011 15:22:24 +0400 (MSD) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Fri, 27 May 2011 15:22:24 +0400 From: Gleb Smirnoff To: Joerg Wunsch Message-ID: <20110527112224.GK74366@FreeBSD.org> References: <20110524060026.E8285AA@uriah.heep.sax.de> <201105240610.p4O6A94E003499@freefall.freebsd.org> <20110526155424.GA90858@uriah.heep.sax.de> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20110526155424.GA90858@uriah.heep.sax.de> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-bugs@FreeBSD.org, FreeBSD-gnats-submit@FreeBSD.org Subject: Re: kern/157287: re0: INVARIANTS panic (Memory modified after free) X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 May 2011 11:22:26 -0000 On Thu, May 26, 2011 at 05:54:24PM +0200, Joerg Wunsch wrote: J> As it turns out this might be related to something else that has been J> using that piece of memory before re(4) is activated, here are the J> boot messages for reference. You can try to add 'options DEBUG_MEMGUARD' to your kernel config, and add the 'vm.memguard.desc=devbuf' to your /boot/loader.conf. This may help to find place where memory is tampered after free. -- Totus tuus, Glebius.