From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 19 18:00:01 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D574016A41F for ; Tue, 19 Jul 2005 18:00:01 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from mv.twc.weather.com (mv.twc.weather.com [65.212.71.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7451143D45 for ; Tue, 19 Jul 2005 18:00:01 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from [10.50.40.201] (Not Verified[65.202.103.25]) by mv.twc.weather.com with NetIQ MailMarshal (v6, 0, 3, 8) id ; Tue, 19 Jul 2005 14:14:16 -0400 From: John Baldwin To: freebsd-hackers@freebsd.org Date: Tue, 19 Jul 2005 11:20:36 -0400 User-Agent: KMail/1.8 References: <20050719034215.GB20752@asx01.verolan.com> In-Reply-To: <20050719034215.GB20752@asx01.verolan.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200507191120.37526.jhb@FreeBSD.org> Cc: Edwin Subject: Re: help w/panic under heavy load - 5.4 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jul 2005 18:00:01 -0000 On Monday 18 July 2005 11:42 pm, Edwin wrote: > Hi, > > I have a recurring (re-producible) panic on the 5.3/5.4 kernels and I would > like to ask for some help in tracking it down. :) - it could be some > misconfig on my part - but i have tried several different configs of the > kernel - ultimately w/ polling on/off, ipfw on/off, ipfastforwarding on/off > - although with ipff off - the box still crashes but in a different > location - it will even crash w/ GENERIC kernel under heavy load. > > I'm not quite sure where to look past the below (ie. what variables/etc to > present to the list). Try turning INVARIANTS and INVARIANT_SUPPORT on in your kernel and see if you can reproduce this. Also, try to get a traceback in ddb if possible as sometimes ddb gives more reliable stack traces. It looks like your m is NULL, in which case the KASSERT() on the previous line should fire if INVARIANTS is on. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org