From owner-freebsd-current@FreeBSD.ORG Mon Nov 17 06:40:09 2003 Return-Path: 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 21EE416A4CE for ; Mon, 17 Nov 2003 06:40:09 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A26E43F93 for ; Mon, 17 Nov 2003 06:40:08 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.9p2/8.12.9) with ESMTP id hAHEc5Mg064441; Mon, 17 Nov 2003 09:38:05 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)hAHEbpqU064431; Mon, 17 Nov 2003 09:38:05 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Mon, 17 Nov 2003 09:37:51 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Jens Rehsack In-Reply-To: <3FB774CF.2010901@liwing.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: Machine freeze when X starts X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Nov 2003 14:40:09 -0000 On Sun, 16 Nov 2003, Jens Rehsack wrote: > after I updated my machine yesterday to the -CURRENT src/ and ports/ of > yesterday (2003-11-15 10:30 GMT), build kernel and world as described in > Kirks HEADSUP mail and rebuild all ports, my machine always crashes when > I start X. > > My problem is, that I cannot determine the reason for the crashes, so I > cannot think about a workaround. Any hints are very welcome :-) > > It doesn't matter if I start using gdm or startx from console, the > workstation switches to graphics mode and stops. I can press keys (eg. > numlock) and there're recognized, but it seems no action is taken. I > cannot kill the server using Ctrl+Alt+Backspace, Ctrl+Alt+Del didn't > reboot, typing 'reset' doesn't do anything and it's not possible to > remote login to the machine for clean reboot. > > The machine answers ping requests and accept incoming packets. A > webserver is running on it and I can telnet to it, but the 'GET / > HTTP/1.0' isn't answered. Hmm. This failure mode is fairly common when a resource deadlock or lock deadlock occurs in some kernel subsystems. Any chance you can get a serial console on the box so you can drop to DDB and generate some ps and stacktrace output? Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories