Date: Sun, 20 Apr 2014 09:20:43 -0600 From: Warner Losh <imp@bsdimp.com> To: Greg Rivers <gcr+freebsd-stable@tharned.org> Cc: Glen Barber <gjb@FreeBSD.org>, FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: vt(4) and geli(8) Message-ID: <7B70F227-DEDF-4123-B855-102290039B0C@gmail.com> In-Reply-To: <alpine.BSF.2.00.1404191107360.1721@angus.tharned.org> References: <alpine.BSF.2.00.1404181026430.12069@roadkill.tharned.org> <5351CEF6.3060007@pobox.com> <CAGE5yCrJ-%2BKdH9%2BpPhsObrh6si-w%2BOMQFL04hU_BrsGJZrDdow@mail.gmail.com> <20140419023539.GO49791@glenbarber.us> <alpine.BSF.2.00.1404191107360.1721@angus.tharned.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 19, 2014, at 10:22 AM, Greg Rivers = <gcr+freebsd-stable@tharned.org> wrote: > On Fri, 18 Apr 2014, Glen Barber wrote: >=20 >> I'm convinced this is a USB issue. When I have a USB keyboard = plugged in to my laptop, I observe the same behavior as Chris (on = 11.0-CURRENT r264302). >>=20 >> When I am prompted to enter the passphrase and do not have the USB = keyboard plugged in (meaning, my laptop built-in keyboard), do not = observe this behavior. >>=20 >=20 > My case doesn't seem to be directly USB related. The laptop where I = see this does not have a USB keyboard. And when I boot without loading = any USB drivers (uhci, ehci) at all, the problem still exists. >=20 > However, I just discovered that if I load the kbdmux driver, it works = as expected. What do you suppose that means? Sure sounds like an interrupt mess that the vt(8) author needs to work = out with the usb author. Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7B70F227-DEDF-4123-B855-102290039B0C>