From owner-freebsd-current@FreeBSD.ORG  Sat Jun 22 04:39:17 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id 5ADB4F38
 for <freebsd-current@freebsd.org>; Sat, 22 Jun 2013 04:39:17 +0000 (UTC)
 (envelope-from fullermd@over-yonder.net)
Received: from thyme.infocus-llc.com (server.infocus-llc.com [206.156.254.44])
 by mx1.freebsd.org (Postfix) with ESMTP id 368E61BC7
 for <freebsd-current@freebsd.org>; Sat, 22 Jun 2013 04:39:16 +0000 (UTC)
Received: from draco.over-yonder.net (c-75-65-60-66.hsd1.ms.comcast.net
 [75.65.60.66])
 (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits))
 (No client certificate requested)
 by thyme.infocus-llc.com (Postfix) with ESMTPSA id 3093F37B51A;
 Fri, 21 Jun 2013 23:39:10 -0500 (CDT)
Received: by draco.over-yonder.net (Postfix, from userid 100)
 id 3bckYn5BhRzDDR; Fri, 21 Jun 2013 23:39:09 -0500 (CDT)
Date: Fri, 21 Jun 2013 23:39:09 -0500
From: "Matthew D. Fuller" <fullermd@over-yonder.net>
To: Miguel Clara <miguelmclara@gmail.com>
Subject: Re: Cannot startx on FreeBSD10 Current
Message-ID: <20130622043909.GC74291@over-yonder.net>
References: <kpfa4f$9j6$1@ger.gmane.org> <51BB3D2A.3070509@gmail.com>
 <op.wyob10gn34t2sn@markf.office.supranet.net>
 <51BB40A5.9090409@gmail.com>
 <op.wyoc2d1e34t2sn@markf.office.supranet.net>
 <51BB4D49.6040603@gmail.com>
 <op.wyofa5f634t2sn@tech304.office.supranet.net>
 <loom.20130622T022435-478@post.gmane.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <loom.20130622T022435-478@post.gmane.org>
X-Editor: vi
X-OS: FreeBSD <http://www.freebsd.org/>
User-Agent: Mutt/1.5.21-fullermd.4 (2010-09-15)
X-Virus-Scanned: clamav-milter 0.97.6 at thyme.infocus-llc.com
X-Virus-Status: Clean
Cc: freebsd-current@freebsd.org
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Jun 2013 04:39:17 -0000

On Sat, Jun 22, 2013 at 12:29:49AM +0000 I heard the voice of
Miguel Clara, and lo! it spake thus:
> 
> The only way to turn off is but "force" and this can cause damage to
> filesystems, this is indeed a very big issue, and I'm not sure if
> its specific to KMS or some freebsd-current problem cause I have no
> way to look into it!

One little trick you might try is to login to a second VTY and run
something like "sleep 60 ; shutdown -r now" before switching back and
running startx; if it's just a UI crash/lockup rather than a
whole-system such, that'll give you a clean reboot without FS damage.
Of course, if it's a whole-system lockup, it won't, but that also
means you can tell which it is, which may be diagnostically useful...

(ssh'ing in from another machine is another way to track such things,
but may be less convenient depending on your own setup...)


-- 
Matthew Fuller     (MF4839)   |  fullermd@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
           On the Internet, nobody can hear you scream.