From owner-freebsd-current@FreeBSD.ORG Fri May 8 09:56:53 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 9134E1CD; Fri, 8 May 2015 09:56:53 +0000 (UTC) Received: from mail-pd0-x22b.google.com (mail-pd0-x22b.google.com [IPv6:2607:f8b0:400e:c02::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5EEF41EFD; Fri, 8 May 2015 09:56:53 +0000 (UTC) Received: by pdea3 with SMTP id a3so75526703pde.3; Fri, 08 May 2015 02:56:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=He/e0Og7iN/Nx2RoEyncH/NuA7g1ciIPpqBMwFwFgNQ=; b=DQ4Ai8+v2w3sNcKU9Wle2u1Cq5Vr3UFwlJv+jfZ89pQfLowOd+QCHOBEOv1BUvN3aI UE577DYxJ5mXZnmDFDFDN2O/Qse5gW0zw+f7GT1sj7Y7iF7eCpX4a62nVPkRE/wZj0M6 s8KqZGIXbpIKnNWIm4y5tpO2Tr5xaKVURXuq3pB9LNKN1TusNtu4SGFg34ggS+jBORHn n3Ys6febgTXLDaP1LoY/dv6NcyT10k1Gmlw+1191yW0L9450sAOwuYwhSyhUMGhUD6pL aaxbrlyPIEZ6uagOxP+r/5pdE0M+pcYECsSMDfEGR5BNTaR3h4n/tP84qtqSxUgsLUjY 48Kg== X-Received: by 10.68.252.38 with SMTP id zp6mr5105659pbc.159.1431078970604; Fri, 08 May 2015 02:56:10 -0700 (PDT) Received: from ?IPv6:2601:8:ab80:7d6:c555:c310:d7f4:96d3? ([2601:8:ab80:7d6:c555:c310:d7f4:96d3]) by mx.google.com with ESMTPSA id mi1sm4562828pab.0.2015.05.08.02.56.09 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 08 May 2015 02:56:09 -0700 (PDT) References: <554B5D11.3080709@selasky.org> <554BC475.50203@selasky.org> <554BD2A8.70702@selasky.org> <554C3CCB.3030809@selasky.org> Mime-Version: 1.0 (1.0) In-Reply-To: <554C3CCB.3030809@selasky.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <4937E44E-C0EF-4052-961C-F46D5EC5BE00@gmail.com> Cc: Kevin Oberman , FreeBSD Current , Ed Maste , Aleksandr Rybalko X-Mailer: iPhone Mail (12F70) From: Garrett Cooper Subject: Re: Race VT+X11 on -current Date: Fri, 8 May 2015 02:56:08 -0700 To: Hans Petter Selasky 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 09:56:53 -0000 > 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