From owner-freebsd-current@FreeBSD.ORG Fri Jun 24 15:38:05 2005 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 5BD5A16A41C for ; Fri, 24 Jun 2005 15:38:05 +0000 (GMT) (envelope-from thierry@herbelot.com) Received: from postfix4-2.free.fr (postfix4-2.free.fr [213.228.0.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D90F43D49 for ; Fri, 24 Jun 2005 15:38:05 +0000 (GMT) (envelope-from thierry@herbelot.com) Received: from herbelot.dyndns.org (bne75-4-82-227-159-103.fbx.proxad.net [82.227.159.103]) by postfix4-2.free.fr (Postfix) with ESMTP id 037A8320279 for ; Fri, 24 Jun 2005 17:38:03 +0200 (CEST) Received: from diversion.herbelot.nom (diversion.herbelot.nom [192.168.2.6]) by herbelot.dyndns.org (8.13.3/8.13.3) with ESMTP id j5OFbw2w020557 for ; Fri, 24 Jun 2005 17:38:02 +0200 (CEST) From: Thierry Herbelot To: freebsd-current@freebsd.org Date: Fri, 24 Jun 2005 17:37:55 +0200 User-Agent: KMail/1.8 References: <200506241626.57469.thierry@herbelot.com> <20050624150350.GA3256@xor.obsecurity.org> In-Reply-To: <20050624150350.GA3256@xor.obsecurity.org> X-Warning: Windows can lose your files X-Op-Sys: Le FriBi de la mort qui tue X-Org: TfH&Co X-MailScanner: Found to be clean MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200506241737.56466.thierry@herbelot.com> Subject: Re: panic: Memory modified after free X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: thierry@herbelot.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jun 2005 15:38:05 -0000 Le Friday 24 June 2005 17:03, Kris Kennaway a écrit : > On Fri, Jun 24, 2005 at 04:26:55PM +0200, Thierry Herbelot wrote: > > This is with an SMP machine (oldish BP6) > > Looks like you forgot to include the full panic...wasn't there a "last > used by FOO" also displayed? If so, you should configure > DEBUG_MEMGUARD to watch this malloc type (some assembly required, but > it's pretty straightforward -- see Bosko Milekic's post to this > mailing list when he committed support describing how to do it) and > try to replicate the panic. sorry if I forgot anything : this is the only message I had on the serial console : [traditional dmesg startup messages] Local package initialization:. Additional TCP options:. Starting background file system checks in 60 seconds. Fri Jun 24 09:10:10 CEST 2005 FreeBSD/i386 (multi-cur.herbelot.nom) (ttyd0) login: Jun 24 09:11:02 multi-cur su: thierry.herbelot to root on /dev/ttyp0 panic: Memory modified after free 0xc15c1400(256) val=0 @ 0xc15c1400 cpuid = 0 KDB: enter: panic [thread pid 520 tid 100070 ] Stopped at kdb_enter+0x2b: nop db> where Tracing pid 520 tid 100070 td 0xc1508780 kdb_enter(c084ecf5) at kdb_enter+0x2b panic(c08695fc,c15c1400,100,0,c15c1400) at panic+0x127 trash_ctor(c15c1400,100,cc89db40,1,c104a9d8) at trash_ctor+0x2f mb_ctor_mbuf(c15c1400,100,cc89db40,1) at mb_ctor_mbuf+0x18 uma_zalloc_arg(c104a9a0,cc89db40,1) at uma_zalloc_arg+0x10f [rest of the ddb session] I forgot to add : this is with a straight GENERIC kernel, built from sources cvsupped around yesterday Jun 23 20:00:00 CEST 2005 the full dmesg is accessible at : http://herbelot.tfh.free.fr/050624.trace Cheers TfH > > Kris