From owner-freebsd-current@FreeBSD.ORG Mon Nov 17 07:18:35 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 A7CAE16A4CF for ; Mon, 17 Nov 2003 07:18:35 -0800 (PST) Received: from mail.liwing.de (mail.liwing.de [213.70.188.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 06F2F43FBD for ; Mon, 17 Nov 2003 07:18:33 -0800 (PST) (envelope-from rehsack@liwing.de) Received: (qmail 57115 invoked from network); 17 Nov 2003 15:18:30 -0000 Received: from stingray.liwing.de (HELO liwing.de) ([213.70.188.164]) (envelope-sender ) by mail.liwing.de (qmail-ldap-1.03) with SMTP for ; 17 Nov 2003 15:18:30 -0000 Message-ID: <3FB8E6C6.6020308@liwing.de> Date: Mon, 17 Nov 2003 15:18:30 +0000 From: Jens Rehsack User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031116 X-Accept-Language: de-de, de, en-us, en MIME-Version: 1.0 To: Robert Watson References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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 15:18:35 -0000 Robert Watson wrote: > 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? It seems to me a little bit more complicated to setup the serial console, so: yes, I can do it, but not today. Or - if you have a small "quick get DDB to serial console without many trouble", I can give it a quick start. I'll try to do this week. Jens