From owner-freebsd-current@FreeBSD.ORG Tue Aug 10 15:38:11 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 D17CE16A4CE for ; Tue, 10 Aug 2004 15:38:11 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5ED1243D54 for ; Tue, 10 Aug 2004 15:38:11 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.11/8.12.11) with ESMTP id i7AFac8C085126; Tue, 10 Aug 2004 11:36:38 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i7AFacRW085123; Tue, 10 Aug 2004 11:36:38 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Tue, 10 Aug 2004 11:36:38 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Martin Blapp In-Reply-To: <20040810121717.X31181@cvs.imp.ch> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: Current is in a very desolated state 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: Tue, 10 Aug 2004 15:38:11 -0000 On Tue, 10 Aug 2004, Martin Blapp wrote: > Even with the disabled preemtion CURRENT is in a very desolated state at > the moment - and this one week before freeze. > > While I was able to run a server with 5.2.1 about 1 month without > panicing, this is no longer true with recent current. > > The panics I get are in the timer codepath or sometimes in the vfs > layer. It's very easy to kill the machine with high load (rm -rfd > /usr/src while running a make world -j 10) kills the server. > > I also get this panic after 20 - 30 minutes load You left out the panic message. In fact, you left out all three panic messages. This will makes it a lot harder to debug the problems you're experiencing. While I'm sure you're already familiar with it, you can find instructions for setting up the debugging environment and making bug reports in the handbook. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research > propagate_priority(c34e3420,0,82b45d4f,16ccf49,ffc00014) at > propagate_priority+0x82 > turnstile_wait(c3bd0480,c09396a0,c3aea840,c35b0680,4) at turnstile_wait+0x325 > _mtx_lock_sleep(c09396a0,c34e3420,0,0,0) at _mtx_lock_sleep+0x122 > ithread_loop(c3460980,de97bd48,0,0,0) at ithread_loop+0x19c > fork_exit(c062a1af,c3460980,de97bd48) at fork_exit+0x80 > fork_trampoline() at fork_trampoline+0x8 > > This is an SMP box with two XEON's, running a SMP kernel with SCHEDBSD. > > Martin > > Martin Blapp, > ------------------------------------------------------------------ > ImproWare AG, UNIXSP & ISP, Zurlindenstrasse 29, 4133 Pratteln, CH > Phone: +41 61 826 93 00 Fax: +41 61 826 93 01 > PGP: > PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E > ------------------------------------------------------------------ > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >