From owner-freebsd-current@FreeBSD.ORG Mon Nov 17 02:44:30 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 9A9E916A4CF for ; Mon, 17 Nov 2003 02:44:30 -0800 (PST) Received: from mail.liwing.de (mail.liwing.de [213.70.188.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5643243FBD for ; Mon, 17 Nov 2003 02:44:29 -0800 (PST) (envelope-from rehsack@liwing.de) Received: (qmail 91572 invoked from network); 17 Nov 2003 10:44:28 -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 10:44:28 -0000 Message-ID: <3FB8A68C.2020505@liwing.de> Date: Mon, 17 Nov 2003 10:44:28 +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: Chris Knight References: <00fc01c3aca4$fe072140$030aa8c0@corp.eeasy.com.au> In-Reply-To: <00fc01c3aca4$fe072140$030aa8c0@corp.eeasy.com.au> 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 10:44:30 -0000 Chris Knight wrote: >>-----Original Message----- >>From: Jens Rehsack [mailto:rehsack@liwing.de] >>Sent: Monday, 17 November 2003 00:00 >>To: current@freebsd.org >>Subject: Machine freeze when X starts >> >> >>Hi, >> >>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 :-) > > I had a similar problem. I "resolved" my problem by killing the gnome > session processes and the X lockup was fixed. I had replaced metacity with > enlightenment, so there might be some weird interaction between the two. > Hope this helps. Hi Chris, sorry, that wont help me out, 'cause the machine is not reacting to anything I'm doing (except the power and reset button). Best regards, Jens