From owner-freebsd-current Thu Nov 7 15: 7:11 2002 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 512EE37B401 for ; Thu, 7 Nov 2002 15:07:10 -0800 (PST) Received: from lakemtao03.cox.net (lakemtao03.cox.net [68.1.17.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 81AE543E4A for ; Thu, 7 Nov 2002 15:07:09 -0800 (PST) (envelope-from ataraxia@cox.net) Received: from arkadia.nv.cox.net ([68.98.181.29]) by lakemtao03.cox.net (InterMail vM.5.01.04.05 201-253-122-122-105-20011231) with ESMTP id <20021107230710.KQVV16428.lakemtao03.cox.net@arkadia.nv.cox.net>; Thu, 7 Nov 2002 18:07:10 -0500 Received: from arkadia.nv.cox.net (localhost [127.0.0.1]) by arkadia.nv.cox.net (8.12.6/8.12.6) with ESMTP id gA7N78V3017126; Thu, 7 Nov 2002 18:07:08 -0500 (EST) (envelope-from ataraxia@arkadia.nv.cox.net) Received: (from ataraxia@localhost) by arkadia.nv.cox.net (8.12.6/8.12.6/Submit) id gA7N78Si017125; Thu, 7 Nov 2002 18:07:08 -0500 (EST) (envelope-from ataraxia) Date: Thu, 7 Nov 2002 18:07:08 -0500 (EST) From: Ray Kohler Message-Id: <200211072307.gA7N78Si017125@arkadia.nv.cox.net> To: current@FreeBSD.ORG, qumqats@outel.org Subject: Re: dnet causes Hard Lock on SMP kernel? ( was 'Why is my -current system Hard Locking?' ) In-Reply-To: <161351601.1036680423@[192.168.1.20]> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > From owner-freebsd-current@FreeBSD.ORG Thu Nov 7 18:00:10 2002 > Date: Thu, 07 Nov 2002 14:47:03 -0800 > From: "Joel M. Baldwin" > To: current@FreeBSD.ORG > Subject: dnet causes Hard Lock on SMP kernel? ( was 'Why is my -current > system Hard Locking?' ) > > > The BIG thing is that I now have a sure fire way of forcing > a Hard Lock. Every time I run the distributed.net client > 'dnet' the system hard locks. BUT ONLY ON A SMP KERNEL! > I have a non SMP kernel running and things so far > seem stable. Running the system with only 1 CPU is slow, > so it'll take a while for me to be sure. > > So the questions now are. > 1.) What is dnet doing that is Hard Locking the system? > 2.) Is the dnet problem the same as what has been causing > my Hard Locks all along? Just a guess, but maybe your system locks up every time the CPU usage gets very high under SMP? That's one thing dnetc is guaranteed to do. Do other CPU-intensive operations do it? (Maybe you said earlier, but I haven't been following this thread.) - @ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message