From owner-freebsd-current@FreeBSD.ORG Sat Jun 22 14:01:04 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 3193F9AA for ; Sat, 22 Jun 2013 14:01:04 +0000 (UTC) (envelope-from miguelmclara@gmail.com) Received: from mail-we0-x233.google.com (mail-we0-x233.google.com [IPv6:2a00:1450:400c:c03::233]) by mx1.freebsd.org (Postfix) with ESMTP id BCA851EFF for ; Sat, 22 Jun 2013 14:01:03 +0000 (UTC) Received: by mail-we0-f179.google.com with SMTP id w59so7220472wes.10 for ; Sat, 22 Jun 2013 07:01:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=O56ij3piM+7XD1JcRsfv6j9O9NTmLXm+eMS8YYkTNdg=; b=oSua/KQkWz2kuz+ix6fSKFpKEq+GS4WlKSOzqsTAJSYRnOMS/Wt1gde0G2dEIokaV0 HLYBmh2VAUOVl7dePH2cwrMSMjLsxTMUDaBwWcXLnbaS/WeNwc5ZVzi2eYk/+x5A2VAc 9Axwfoz8qT0AZQUqJChX9y+7W2/n1Lv126V9YUhxMngocGhAz6uHajw4o6WJSxepRdi6 TV4Q7AmpVsIQnd5kNhsisgz9hsqCDIhLTHLGzZRG3BrbmCCEsqVCQ0QpaMEYHLHjRtly gHVWAuwc9c2Tt4DCwnYYdRVzQieHo3oK+xpDcDCpVWdUnQAgTvkB4AEuquWMJsUJoriy EqVA== X-Received: by 10.195.12.133 with SMTP id eq5mr12065831wjd.27.1371909662185; Sat, 22 Jun 2013 07:01:02 -0700 (PDT) Received: from [10.10.50.2] (bl6-95-143.dsl.telepac.pt. [82.155.95.143]) by mx.google.com with ESMTPSA id fo10sm4131851wib.8.2013.06.22.07.01.01 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 22 Jun 2013 07:01:01 -0700 (PDT) Message-ID: <51C5BC2B.2090608@gmail.com> Date: Sat, 22 Jun 2013 15:00:59 +0000 From: Miguel Clara User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130613 Thunderbird/17.0.6 MIME-Version: 1.0 To: "Matthew D. Fuller" Subject: Re: Cannot startx on FreeBSD10 Current References: <51BB3D2A.3070509@gmail.com> <51BB40A5.9090409@gmail.com> <51BB4D49.6040603@gmail.com> <20130622043909.GC74291@over-yonder.net> In-Reply-To: <20130622043909.GC74291@over-yonder.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jun 2013 14:01:04 -0000 On Sat Jun 22 04:39:09 2013, Matthew D. Fuller wrote: > 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...) > > I tried the ssh trick, first thing that crossed my mind... but its no good after the reboot or shutdown, I guess by then sshd is not running anymore but I have no way to know! I know this is something in active development but this seams to be of significant importance, I wish I could help somehow but I can't even see what's happening!