From owner-freebsd-stable@FreeBSD.ORG Fri Apr 11 11:43:13 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6AE19ACD; Fri, 11 Apr 2014 11:43:13 +0000 (UTC) Received: from smtp.dlink.ua (smtp.dlink.ua [193.138.187.146]) by mx1.freebsd.org (Postfix) with ESMTP id 245681BE7; Fri, 11 Apr 2014 11:43:12 +0000 (UTC) Received: from terran (unknown [192.168.99.1]) (Authenticated sender: ray) by smtp.dlink.ua (Postfix) with ESMTPA id B6170C4968; Fri, 11 Apr 2014 14:43:11 +0300 (EEST) Date: Fri, 11 Apr 2014 14:45:41 +0300 From: Aleksandr Rybalko To: Glen Barber Subject: Re: Minor vt issue (probably a race) Message-Id: <20140411144541.f22a46af95a8f89e62381e9a@freebsd.org> In-Reply-To: <20140411000147.GA11570@glenbarber.us> References: <20140411000147.GA11570@glenbarber.us> X-Mailer: Sylpheed 3.3.1 (GTK+ 2.24.22; amd64-portbld-freebsd9.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Kevin Oberman , Aleksandr Rybalko , FreeBSD-STABLE Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Apr 2014 11:43:13 -0000 On Thu, 10 Apr 2014 20:01:47 -0400 Glen Barber wrote: > On Thu, Apr 10, 2014 at 04:58:51PM -0700, Kevin Oberman wrote: > > vt has been working for me for a while, but I have encountered an annoying > > issue. Only a little annoying, but it looks like a race and my have less > > obvious impacts. Since the patch to prevent crashes when resuming with vt, > > I have seen the problem. > > > > When I suspend, the system sometimes switches to vty0 before suspending, > > but often does not. When it fails to switch on suspend, it does so a few > > seconds after resume. I have been able to simply switch back to X > > () and everything was normal. If that i its only impact, it's no > > big deal, but I fear that this may have deeper implications that I don't > > see, so I wanted to report it. > > I've seen this too. But, it's been too inconsistent for me to report. > > The other thing I noticed, maybe unrelated, is X is no longer "laggy" > for me after resume since the relevant commit. > > Related? I have no idea. > > Glen > Hi, Glen, if you about broken Xorg screen, then I should say - kern.vt.suspendswitch sysctl designed to help with that. So if you have value other than zero, machine going to ttyv0 before suspend, and back on resume. This is make notification to Xorg or drm to redraw (maybe even reallocate FB memory used by Xorg). Kevin, thanks for report, I will look what happen in that case. It maybe related to some busyness, Xorg's or whole machine, so Xorg do not answers vt(4)'s request to VT switch. Thanks a lot! WBW -- Aleksandr Rybalko