Date: Fri, 08 May 2015 12:07:39 +0200 From: Hans Petter Selasky <hps@selasky.org> To: Garrett Cooper <yaneurabeya@gmail.com> Cc: Kevin Oberman <rkoberman@gmail.com>, FreeBSD Current <freebsd-current@freebsd.org>, Ed Maste <emaste@freebsd.org>, Aleksandr Rybalko <ray@FreeBSD.org> Subject: Re: Race VT+X11 on -current Message-ID: <554C8AEB.2080502@selasky.org> In-Reply-To: <4937E44E-C0EF-4052-961C-F46D5EC5BE00@gmail.com> References: <554B5D11.3080709@selasky.org> <CAN6yY1vno%2B-nV9zBYp11A=F-vAURbhraEFyQR_ue4W7h8pQUMw@mail.gmail.com> <AA8B24D1-DF5A-42CD-8755-15EF3C46E760@gmail.com> <554BC475.50203@selasky.org> <554BD2A8.70702@selasky.org> <554C3CCB.3030809@selasky.org> <4937E44E-C0EF-4052-961C-F46D5EC5BE00@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 05/08/15 11:56, Garrett Cooper wrote: > >> On May 7, 2015, at 21:34, Hans Petter Selasky <hps@selasky.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?554C8AEB.2080502>