From owner-freebsd-current@FreeBSD.ORG Wed Jun 29 04:18:55 2005 Return-Path: X-Original-To: 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 04A1516A41C for ; Wed, 29 Jun 2005 04:18:55 +0000 (GMT) (envelope-from caelian@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF24B43D1D for ; Wed, 29 Jun 2005 04:18:54 +0000 (GMT) (envelope-from caelian@gmail.com) Received: by zproxy.gmail.com with SMTP id o1so441403nzf for ; Tue, 28 Jun 2005 21:18:54 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=llUZaiCsHe6Wo8g7FzfmLxixgBNpkAcwNB9gOhvYmE6eqzNnrn13/Z+FADUo9+Du0ZNpwQCmf/ReXRDkxpS7GOP1enAbl4ya0to0es0gT33WgckhWom16CXXhbSziJ9TRsE6OSucYFiB9Y3N6U0bQzM0ZWhPkJMrYfaSDgE81Qg= Received: by 10.36.89.18 with SMTP id m18mr5318881nzb; Tue, 28 Jun 2005 21:18:53 -0700 (PDT) Received: by 10.36.42.19 with HTTP; Tue, 28 Jun 2005 21:18:52 -0700 (PDT) Message-ID: Date: Tue, 28 Jun 2005 21:18:52 -0700 From: Pascal Hofstee To: Mike Silbersack In-Reply-To: <20050626184415.K9438@odysseus.silby.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20050626184415.K9438@odysseus.silby.com> Cc: current@freebsd.org Subject: Re: mbuf trash panic turned into a printf for now X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Pascal Hofstee List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2005 04:18:55 -0000 On 6/26/05, Mike Silbersack wrote: >=20 > Since the mbuf trash panic is being reported more often now, and we > haven't tracked down why yet, I've turned it into a printf for now. This > means that it's safe to upgrade to -current even if you might be affected= . > :) >=20 > And the more reports, the better, keep them coming if you see the "Memory > modified after free" message. Well .. i just updated my system to today's CURRENT and now (for the first time) see a whole host of "Memory modified after free" messages ... i tried breaking into the debugger .. but apparently KDB doesn't exactly like USB keyboards .. as the second i entered the debugger my keyboard no longer worked and i had to push the reset button. Below is part of the list of messages i have been seeing: ------ Memory modified after free 0xffffff003d640800(256) val=3D2cc0de @ 0xffffff003d64088c Memory modified after free 0xffffff003d45fc00(256) val=3D2cc0de @ 0xffffff003d45fc8c Memory modified after free 0xffffff003d640200(256) val=3D2cc0de @ 0xffffff003d6402b8 Memory modified after free 0xffffff003caa3000(256) val=3D2cc0de @ 0xffffff003caa30c0 Memory modified after free 0xffffff003d45f400(256) val=3D2cc0de @ 0xffffff003d45f48c Memory modified after free 0xffffff003d640400(256) val=3D2cc0de @ 0xffffff003d640474 Memory modified after free 0xffffff003d640700(256) val=3D2cc0de @ 0xffffff003d64078c Memory modified after free 0xffffff003d640a00(256) val=3D2cc0de @ 0xffffff003d640a84 Memory modified after free 0xffffff003d761100(256) val=3D2cc0de @ 0xffffff003d761174 Memory modified after free 0xffffff003d761500(256) val=3D2cc0de @ 0xffffff003d761584 Memory modified after free 0xffffff003d761d00(256) val=3D2cc0de @ 0xffffff003d761d94 Memory modified after free 0xffffff003ca22200(256) val=3D2cc0de @ 0xffffff003ca22294 Memory modified after free 0xffffff003ca22600(256) val=3D2cc0de @ 0xffffff003ca2268c Memory modified after free 0xffffff003ca22a00(256) val=3D2cc0de @ 0xffffff003ca22a8c ------ and the list goes on and on .. though apparently the "value" is Always 2cc0de in my case. To clarify i have never been plagued by the actual mbuf-panic ... just now after updating to todays CURRENT i am seeing these INVARIANT messages If you have suggestions on how i can provide additional details please let me know :) --=20 Pascal Hofstee