From owner-freebsd-current Thu Nov 7 14:55:44 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 22E4037B401 for ; Thu, 7 Nov 2002 14:55:43 -0800 (PST) Received: from outel.org (outel.org [168.150.177.152]) by mx1.FreeBSD.org (Postfix) with ESMTP id B483B43E75 for ; Thu, 7 Nov 2002 14:55:42 -0800 (PST) (envelope-from qumqats@outel.org) Received: from localhost (winxp [192.168.1.20]) by outel.org (8.12.6/8.12.6) with ESMTP id gA7Mtdbu094235 for ; Thu, 7 Nov 2002 14:55:42 -0800 (PST) (envelope-from qumqats@outel.org) 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?' ) Message-ID: <161351601.1036680423@[192.168.1.20]> X-Mailer: Mulberry/3.0.0b8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline 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 I'm still pursuing the cause of the Hard Locks on my system. 1.) I have a serial console hooked up. Nothing appears on the console when a Hard Lock happens. No panic. 2.) Shorting IOCHK to ground on the ISA connector doesn't work on a ABIT BP6, so I can't force myself into ddb. 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? 3.) What is the fix? ADVthaAnksNCE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message