From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 09:00:23 2004 Return-Path: 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 5D2DB16A4CE for ; Fri, 19 Nov 2004 09:00:23 +0000 (GMT) Received: from mail19.syd.optusnet.com.au (mail19.syd.optusnet.com.au [211.29.132.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0405A43D31 for ; Fri, 19 Nov 2004 09:00:22 +0000 (GMT) (envelope-from fbsd-current@mawer.org) Received: from c211-30-90-140.belrs3.nsw.optusnet.com.au (c211-30-95-252.belrs3.nsw.optusnet.com.au [211.30.95.252]) iAJ90K8X016404 for ; Fri, 19 Nov 2004 20:00:20 +1100 Received: (qmail 57256 invoked from network); 19 Nov 2004 09:00:20 -0000 Received: from unknown (HELO ?10.1.1.1?) (unknown) by unknown with SMTP; 19 Nov 2004 09:00:20 -0000 Message-ID: <419DB630.6060402@mawer.org> Date: Fri, 19 Nov 2004 20:00:32 +1100 From: Antony Mawer User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Peter Holm References: <20041112123343.GA12048@peter.osted.lan> <200411151546.15533.jhb@FreeBSD.org> <20041119075924.GA22320@peter.osted.lan> In-Reply-To: <20041119075924.GA22320@peter.osted.lan> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@FreeBSD.org cc: John Baldwin Subject: Re: Freeze X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 19 Nov 2004 09:00:23 -0000 On 19/11/2004 6:59 PM, Peter Holm wrote: > On Mon, Nov 15, 2004 at 03:46:15PM -0500, John Baldwin wrote: >>On Friday 12 November 2004 07:33 am, Peter Holm wrote: >>>GENERIC HEAD from Nov 11 08:05 UTC >>> >>>The following stack traces etc. was done before my first >>>cup of coffee, so it's not so informative as it could have been :-( >>> >>>The test box appeared to have been frozen for more than 6 hours, >>>but was pingable. >>> >>>http://www.holm.cc/stress/log/cons86.html >> >>A weak guess is that you have the system in some sort of livelock due to >>fork()? Have you tried running with 'debug.mpsafevm=1' set from the loader? > > OK, I've got some more info: > > http://www.holm.cc/stress/log/cons88.html > > Looks like a spin in uma_zone_slab() when slab_zalloc() fails? I thought that sounded vaguely familiar -- not sure if it's relevant but I did see that Lukas (le@) had pointed to freezes that looked to be in the similar area (going off the backtrace he posted). I haven't looked into it at all but thought it might be relevant to someone looking at the issue: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=413571+0+current/freebsd-stable Cheers Antony