From owner-freebsd-current@FreeBSD.ORG Fri May 8 10:07:04 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D04458F8; Fri, 8 May 2015 10:07:04 +0000 (UTC) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8EAAC1069; Fri, 8 May 2015 10:07:04 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 6CDBC1FE023; Fri, 8 May 2015 12:06:55 +0200 (CEST) Message-ID: <554C8AEB.2080502@selasky.org> Date: Fri, 08 May 2015 12:07:39 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Garrett Cooper CC: Kevin Oberman , FreeBSD Current , Ed Maste , Aleksandr Rybalko Subject: Re: Race VT+X11 on -current References: <554B5D11.3080709@selasky.org> <554BC475.50203@selasky.org> <554BD2A8.70702@selasky.org> <554C3CCB.3030809@selasky.org> <4937E44E-C0EF-4052-961C-F46D5EC5BE00@gmail.com> In-Reply-To: <4937E44E-C0EF-4052-961C-F46D5EC5BE00@gmail.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 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: Fri, 08 May 2015 10:07:04 -0000 On 05/08/15 11:56, Garrett Cooper wrote: > >> On May 7, 2015, at 21:34, Hans Petter Selasky wrote: >> >> Hi, >> >> I have a fix, attached. >> >> I'll just throw this in if nobody objects. Seems like a trivial issue: >> >> Prevent switching to NULL or own window in the "vt_proc_window_switch" >> function. This fixes an issue where X11 keyboard input can appear >> stuck. The cause of the problem is a duplicate TTY device window >> switch IOCTL during boot, which leaves the "vt_switch_timer" running, >> because the current window is already selected. While at it factor out >> some NULL checks. >> >> PR: 200032 >> Reported by: multiple people >> MFC after: 1 week > > Hi Hans, > Can you please toss that up on phabricator? > Thanks! > -NGie If it helps getting the stuff committed ... https://reviews.freebsd.org/D2480 --HPS