Date: Fri, 08 May 2015 10:29:21 -0400 From: Allan Jude <allanjude@freebsd.org> To: freebsd-current@freebsd.org Subject: Re: Race VT+X11 on -current Message-ID: <554CC841.60908@freebsd.org> In-Reply-To: <554C8AEB.2080502@selasky.org> 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> <554C8AEB.2080502@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --RxEQL24akg37KpJTHsIS3FPdCLQ0LVfa2 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2015-05-08 06:07, Hans Petter Selasky wrote: > 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 ou= t >>> 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 >=20 > If it helps getting the stuff committed ... >=20 > https://reviews.freebsd.org/D2480 >=20 > --HPS > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" My experience is a little different. When suspend/resuming my laptop (Lenovo T530 with nVidia gpu) Sometimes when I resume, it seems like the keyboard is frozen. If I alt+f1, then alt+f9, it seems to work fine after that. I'd never though of trying just alt+f9 right away, as I could already see my X session. Not sure if this is related, but it sounds very similar. --=20 Allan Jude --RxEQL24akg37KpJTHsIS3FPdCLQ0LVfa2 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJVTMhJAAoJEJrBFpNRJZKfTJAP+gOX+rLi425H3re1EmOSgN2q Xu+1yV43DXH0MTF+FU7NshZx8WlTZCcc+YsqY7suOn3tThHQ3YqNJmTg3GPGe3lC NHJP5YdfK2qj3pvSKDPfz1heEXwx8zo4EnLcfw6KLwm4BnqvzKEwThyNs5FKgjYf TJKWMAZCAd2KOfoVJpqNYEb6u7n5UHdlJSdNewrUyE5yJnAGxRDTIIRUQtRKiPs+ i5eIB+jygrOPU8fQM/pqKA1aYhrbAfTmgV7Ip3q+J+58cVUiQf9pxz6t63uoYtV/ CxMwFs45qytnQCdVg/Fb90x8IaLZRFWc1smJRaMUIZx2JDPFLu0d8Da8rKy8dLWF QvqgLNsADnoIictlSFpGzpJf6gcWjFJa9SQNJYwCOktbLIf8fzL0IKBEW7UyEXOF rgynGViZ3Ii0azScokLpOvazmdf/IeouWJOoJalQUKSt1CZmSRgPaQghbCWZyATo m0njPqEh4C5BQ9l5Plalx460UNVrTVieX3IzKk4GMNGJZQeJh/tvgx7+4HbYrE/J Y65tGISkTbV2bxWPGiJLxR8f+RSx18yNcegnIrHRIOHxHAmuYyJItTucOFnWkwPj k/TFOY5uPPBm09ZA1rHqIC6ORmex8vH9o6hO1WYcPQcS/z0e67kb6cuvcc4q4bkT Lvd1rdO1OqVd1XUN1hdq =ZDQQ -----END PGP SIGNATURE----- --RxEQL24akg37KpJTHsIS3FPdCLQ0LVfa2--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?554CC841.60908>