From owner-freebsd-stable@FreeBSD.ORG Fri Jul 1 17:54:07 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org 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 AD56816A41C; Fri, 1 Jul 2005 17:54:07 +0000 (GMT) (envelope-from gmulder@infotechfl.com) Received: from pigeon.infotechfl.com (mailrelay.infotechfl.com [209.251.147.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 46D6243D4C; Fri, 1 Jul 2005 17:54:06 +0000 (GMT) (envelope-from gmulder@infotechfl.com) Received: from [172.20.0.75] (gmulder.infotechfl.com [172.20.0.75]) by pigeon.infotechfl.com (8.11.6/8.11.6) with ESMTP id j61Hs5026036; Fri, 1 Jul 2005 13:54:06 -0400 Message-ID: <42C58373.60008@infotechfl.com> Date: Fri, 01 Jul 2005 13:54:59 -0400 From: Gary Mu1der User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Gleb Smirnoff References: <20050621070427.GA738@obiwan.tataz.chchile.org> <20050621090701.GB34406@cell.sick.ru> <20050621105154.GA36538@cell.sick.ru> <42B961B9.7A5856B3@freebsd.org> <20050623104230.GB61389@cell.sick.ru> <20050623141514.GD738@obiwan.tataz.chchile.org> <42BC5EE2.2020003@infotechfl.com> <20050627082958.GB97832@cell.sick.ru> <42C16BBF.4060107@infotechfl.com> <20050701085808.GD52023@cell.sick.ru> In-Reply-To: <20050701085808.GD52023@cell.sick.ru> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org Subject: Re: panic in RELENG_5 UMA - two new stack traces X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 01 Jul 2005 17:54:07 -0000 Gleb Smirnoff wrote: > On Tue, Jun 28, 2005 at 11:24:47AM -0400, Gary Mu1der wrote: > G> I spent the day yesterday trying to reproduce the crash that I posted > G> last week and you kindly replied to. This is due to the fact that I > G> stupidly managed to overwrite the kernel.debug that I used to generate > G> the stack trace. Sadly I could not cause the system to crash again with > G> the same sb* errors. > G> > G> I did however remove both the Berkley Packet Filter and IPFilter from my > G> custom kernel to try and isolate the problem. This has caused the crash > G> to occur in a different and more reproducible form. I have both > G> INVARIANTS and WITNESS enabled, as you can see from my kernel conf. > G> which is included at the end of this e-mail. > G> > G> Below are the latest stack traces (using bge and then fxp NICs), kernel > G> conf. and dmesg. Any help would be appreciated. This time I have a copy > G> of both the core files and corresponding kernel.debug so I can hopefully > G> provide you with any info you need. > > How often does it crash? Does debug.mpsafenet=0 increases stability? I can reproduce the crash within 60 seconds of firing off 30+ ping/arp -d scripts, all running in parallel. debug.mpsafenet=0 seems to have solved the problem. I'm running 100+ instances of the above script and the system has been stable for over an hour. As I wanted some background on what "debug.mpsafenet=0" does, I did some Googling and found a good write up here: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/current/2004-08/2280.html Thanks, Gary