From owner-freebsd-current Tue Nov 5 21:31: 0 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 0B85137B401 for ; Tue, 5 Nov 2002 21:30:59 -0800 (PST) Received: from outel.org (outel.org [168.150.177.152]) by mx1.FreeBSD.org (Postfix) with ESMTP id A38B743E42 for ; Tue, 5 Nov 2002 21:30:58 -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 gA65UZ9A003320 for ; Tue, 5 Nov 2002 21:30:46 -0800 (PST) (envelope-from qumqats@outel.org) Date: Tue, 05 Nov 2002 21:22:29 -0800 From: "Joel M. Baldwin" To: current@FreeBSD.ORG Subject: Re: Why is my -current system Hard Locking? Message-ID: <12276963.1036531349@[192.168.1.20]> In-Reply-To: <200211060525.gA65PPIg032862@troutmask.apl.washington.edu> References: <200211060525.gA65PPIg032862@troutmask.apl.washington.edu> 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 There isn't any indication of a panic. The system just locks up and is non responsive. --On Tuesday, November 05, 2002 9:25 PM -0800 Steve Kargl wrote: >> >> This sounds good, but isn't it. X doesn't have control of the >> graphics and kbd on my system. Only xdm and clients are running, >> the server is on another system. When panics happen ( and they have >> ) I get the message on the screen. >> >> Also this problem has been happening both with X running and not. >> >> Any other suggestions? >> > > If it happens without X running, then you should > drop into the debugger and get a backtrace and > crash dump. Do you have known method of inducing > the panic? > > -- > Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message