Date: Thu, 7 Nov 2002 18:07:08 -0500 (EST) From: Ray Kohler <ataraxia@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?' ) Message-ID: <200211072307.gA7N78Si017125@arkadia.nv.cox.net> In-Reply-To: <161351601.1036680423@[192.168.1.20]>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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" <qumqats@outel.org> > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200211072307.gA7N78Si017125>