From owner-freebsd-current@FreeBSD.ORG Sun Jun 26 23:46:01 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 C5D6F16A41C for ; Sun, 26 Jun 2005 23:46:01 +0000 (GMT) (envelope-from silby@silby.com) Received: from relay03.pair.com (relay03.pair.com [209.68.5.17]) by mx1.FreeBSD.org (Postfix) with SMTP id 9084A43D49 for ; Sun, 26 Jun 2005 23:46:01 +0000 (GMT) (envelope-from silby@silby.com) Received: (qmail 82647 invoked from network); 26 Jun 2005 23:45:58 -0000 Received: from unknown (HELO localhost) (unknown) by unknown with SMTP; 26 Jun 2005 23:45:58 -0000 X-pair-Authenticated: 209.68.2.70 Date: Sun, 26 Jun 2005 18:45:42 -0500 (CDT) From: Mike Silbersack To: current@freebsd.org Message-ID: <20050626184415.K9438@odysseus.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Subject: mbuf trash panic turned into a printf for now X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Jun 2005 23:46:01 -0000 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. :) And the more reports, the better, keep them coming if you see the "Memory modified after free" message. Mike "Silby" Silbersack