From owner-freebsd-current Wed Nov 6 14:55:45 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 1EB6F37B401 for ; Wed, 6 Nov 2002 14:55:44 -0800 (PST) Received: from outel.org (outel.org [168.150.177.152]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A31F43E4A for ; Wed, 6 Nov 2002 14:55:43 -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 gA6Mt4Om057459 for ; Wed, 6 Nov 2002 14:55:18 -0800 (PST) (envelope-from qumqats@outel.org) Date: Wed, 06 Nov 2002 14:46:39 -0800 From: "Joel M. Baldwin" To: current@FreeBSD.ORG Subject: Re: Why is my -current system Hard Locking? Message-ID: <74927039.1036593999@[192.168.1.20]> In-Reply-To: <149469335.1036439809@[192.168.1.20]> References: <149469335.1036439809@[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 No change, the system is still Hard Locking. It did it 4 times yesterday. The next steps for me are: 1.) Get a serial console working. Maybe I'll get some indication of what's happening that way. 2.) When the serial console is working, see if I can break into ddb after a Hard Lock. Is there a way in HARDWARE to FORCE a break into ddb? ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Maybe I can tell if the system is running, where it is running, and how it got there. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message