From owner-freebsd-hackers@FreeBSD.ORG Fri Oct 14 13:57:56 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 E893C16A41F; Fri, 14 Oct 2005 13:57:56 +0000 (GMT) (envelope-from rob@thing.net) Received: from daemon.mistermishap.net (167-49.nyc.dsl.access.net [166.84.167.49]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43C0343D48; Fri, 14 Oct 2005 13:57:55 +0000 (GMT) (envelope-from rob@thing.net) Received: from daemon.mistermishap.net (localhost.mistermishap.net [127.0.0.1]) by daemon.mistermishap.net (8.12.9/8.12.9) with ESMTP id j9EDvtmU067678; Fri, 14 Oct 2005 09:57:55 -0400 (EDT) (envelope-from rob@thing.net) Received: from localhost (rob@localhost) by daemon.mistermishap.net (8.12.9/8.12.9/Submit) with ESMTP id j9EDvtlw067675; Fri, 14 Oct 2005 09:57:55 -0400 (EDT) X-Authentication-Warning: daemon.mistermishap.net: rob owned process doing -bs Date: Fri, 14 Oct 2005 09:57:55 -0400 (EDT) From: Rob Watt X-X-Sender: rob@daemon.mistermishap.net To: Don Lewis In-Reply-To: <20051013080849.F60486@daemon.mistermishap.net> Message-ID: <20051014092702.V67464@daemon.mistermishap.net> References: <200510121925.j9CJPU5D048710@gw.catspoiler.org> <20051013080849.F60486@daemon.mistermishap.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailman-Approved-At: Sat, 15 Oct 2005 13:03:42 +0000 Cc: rob work , mikep@hudson-trading.com, freebsd-hackers@freebsd.org, Jason Carroll Subject: Re: freebsd-5.4-stable panics 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: Fri, 14 Oct 2005 13:57:57 -0000 On Thu, 13 Oct 2005, Rob Watt wrote: > The test machine did panic. Unfortunately I was not running with > BREAK_TO_DEBUGGER. I will re-run the tests with all of the debugging > options we were using before, and then send you the trace info. Unfortunately I was not able to reproduce the panics with BREAK_TO_DEBUGGER compiled into the kernel. I have no log messages or core info from the first panic/reboot. We've been having other problems with our 5 machines, so it's possible (and likely) that the reboot I saw was unrelated to your patch. I ran our stress tests for about 14 more hours without incident. Before we were able to trigger the kern_proc bug on a 6.0 machine within 0-2 hours. We've only experienced the kern_proc bug in 6.0. The bugs we've experienced in 5.4 are multicast/network-threading related. So unfortunately the only thing we can really test for is whether the machine is still stable with your patch. I've had to put all of my test machines back into production running 6.0. If I can free a 5 SMP machine for more tests, I will do so, but at this point it would good if someone else can test the 5.4 patch. I can't post our simulations, but something similar to Antoine Pelisse's test program should be sufficient to see if the patch works. thanks for your help. - Rob Watt