From owner-freebsd-x11@FreeBSD.ORG Sun Jun 19 18:12:06 2011 Return-Path: Delivered-To: x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D82F7106564A for ; Sun, 19 Jun 2011 18:12:06 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 987CC8FC1B for ; Sun, 19 Jun 2011 18:12:06 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.4/8.14.4) with ESMTP id p5JIC5rK040758; Sun, 19 Jun 2011 12:12:05 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.4/8.14.4/Submit) with ESMTP id p5JIC5S4040755; Sun, 19 Jun 2011 12:12:05 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Sun, 19 Jun 2011 12:12:05 -0600 (MDT) From: Warren Block To: Robert Huff In-Reply-To: <19966.10876.116435.581973@jerusalem.litteratus.org> Message-ID: References: <19963.63779.628334.773399@jerusalem.litteratus.org> <19965.59049.213026.726788@jerusalem.litteratus.org> <19966.10876.116435.581973@jerusalem.litteratus.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Sun, 19 Jun 2011 12:12:05 -0600 (MDT) Cc: x11@freebsd.org Subject: Re: can't (re)start X, may be hal related X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Jun 2011 18:12:06 -0000 On Sun, 19 Jun 2011, Robert Huff wrote: > > Warren Block writes: > >> So it's not a hal problem. >> >> > However: the (EE) line is gone from Xorg.0.log. >> > I am now looking at this from the end of xdm.log: >> > >> > XIO: fatal IO error 35 (Resource temporarily unavailable) on X server ":0.0" >> > after 169 requests (131 known processed) with 0 events remaining. >> > xdm error (pid 10712): Display :0 is being disabled >> >> Those are "normal" errors. Running glxgears from a console and >> closing the gear window with the mouse produces them, too. > > Which leaves this back where it was: broken, with no path to > diagnosis. The next step would be to disable xdm and see if starting and restarting X with startx has the same problem.