From owner-freebsd-current Thu Nov 7 15:29:51 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 661F437B401 for ; Thu, 7 Nov 2002 15:29:50 -0800 (PST) Received: from tinker.exit.com (tinker.exit.com [206.223.0.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id C40C743E42 for ; Thu, 7 Nov 2002 15:29:49 -0800 (PST) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime [206.223.0.5]) by tinker.exit.com (8.12.5/8.12.5) with ESMTP id gA7NTgUl084132; Thu, 7 Nov 2002 15:29:42 -0800 (PST) (envelope-from frank@exit.com) Received: from realtime.exit.com (localhost [127.0.0.1]) by realtime.exit.com (8.12.6/8.12.2) with ESMTP id gA7NTgbk042702; Thu, 7 Nov 2002 15:29:42 -0800 (PST) (envelope-from frank@realtime.exit.com) Received: (from frank@localhost) by realtime.exit.com (8.12.6/8.12.6/Submit) id gA7NTg98042701; Thu, 7 Nov 2002 15:29:42 -0800 (PST) From: Frank Mayhar Message-Id: <200211072329.gA7NTg98042701@realtime.exit.com> Subject: Re: dnet causes Hard Lock on SMP kernel? ( was 'Why is my -current system Hard Locking?' ) In-Reply-To: <200211072307.gA7N78Si017125@arkadia.nv.cox.net> To: Ray Kohler Date: Thu, 7 Nov 2002 15:29:42 -0800 (PST) Cc: current@FreeBSD.ORG, qumqats@outel.org Reply-To: frank@exit.com X-Copyright0: Copyright 2002 Frank Mayhar. All Rights Reserved. X-Copyright1: Permission granted for electronic reproduction as Usenet News or email only. X-Mailer: ELM [version 2.4ME+ PL99b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII 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 Ray Kohler wrote: > 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.) That is, in fact, the case, at least with my system. It usually eventually unhangs on its own, but sometimes it's a hard wedge that only the reset button can fix. This is in -stable, btw. Is it happening in -current as well? -- Frank Mayhar frank@exit.com http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message