From owner-freebsd-current@FreeBSD.ORG Fri Jun 24 20:01:52 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 0E20116A41C for ; Fri, 24 Jun 2005 20:01:52 +0000 (GMT) (envelope-from silby@silby.com) Received: from relay02.pair.com (relay02.pair.com [209.68.5.16]) by mx1.FreeBSD.org (Postfix) with SMTP id CEBD843D49 for ; Fri, 24 Jun 2005 20:01:51 +0000 (GMT) (envelope-from silby@silby.com) Received: (qmail 93472 invoked from network); 24 Jun 2005 20:01:50 -0000 Received: from unknown (HELO localhost) (unknown) by unknown with SMTP; 24 Jun 2005 20:01:50 -0000 X-pair-Authenticated: 209.68.2.70 Date: Fri, 24 Jun 2005 15:01:34 -0500 (CDT) From: Mike Silbersack To: Thierry Herbelot , Peter Holm Message-ID: <20050624145923.P83036@odysseus.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: current@freebsd.org Subject: re: new panics 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: Fri, 24 Jun 2005 20:01:52 -0000 The Memory modified after free panics you guys have reported are unfortunately not pinpointing where the error occured, they're just pinpointing where the error was detected. :) So, either I need to improve the code to be more useful, or we could do some quick code inspection - which network devices are you using, and are you using any features like ipfw, netgraph, etc? Mike "Silby" Silbersack