From owner-freebsd-stable@FreeBSD.ORG Fri May 20 13:10:33 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 09A0D16A4CE; Fri, 20 May 2005 13:10:33 +0000 (GMT) Received: from postfix3-1.free.fr (postfix3-1.free.fr [213.228.0.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13E7B43D9C; Fri, 20 May 2005 13:10:32 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (vol75-8-82-233-239-98.fbx.proxad.net [82.233.239.98]) by postfix3-1.free.fr (Postfix) with ESMTP id 2792A1734C5; Fri, 20 May 2005 15:10:31 +0200 (CEST) Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id 1F388405B; Fri, 20 May 2005 15:10:32 +0200 (CEST) Date: Fri, 20 May 2005 15:10:32 +0200 From: Jeremie Le Hen To: Gleb Smirnoff Message-ID: <20050520131031.GU818@obiwan.tataz.chchile.org> References: <20050515120007.GA777@obiwan.tataz.chchile.org> <20050518155130.H87264@carver.gumbysoft.com> <20050519125639.GK818@obiwan.tataz.chchile.org> <20050520080435.GB26938@cell.sick.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050520080435.GB26938@cell.sick.ru> User-Agent: Mutt/1.5.9i cc: Jeremie Le Hen cc: freebsd-stable@FreeBSD.org Subject: Re: panic in recent RELENG_5 tcp code path X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 May 2005 13:10:33 -0000 Hi Gleb, > according to the fact that the panic occured in dereferncing mbuf pointer > your kernel is compiled without INVARIANTS. > > Please compile it with INVARIANTS. This will probably help to trigger panic > earlier, and it will be more clear. a quick look at src/conf/NOTES reveals the following : %%% # # The INVARIANTS option is used in a number of source files to enable # extra sanity checking of internal structures. This support is not # enabled by default because of the extra time it would take to check # for these conditions, which can only occur as a result of # programming errors. # %%% I'm going to recompile my kernel with INVARIANTS but I wonder in which order of magniture it will slow my kernel down. In other words, what does INVARIANTS do concretely, shall I expect a performance drop like WITNESS does ? Best regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org >