Date: Sun, 20 Apr 2014 09:19:52 -0600 From: Warner Losh <imp@bsdimp.com> To: Peter Wemm <peter@wemm.org> Cc: Chris Nehren <cnehren+freebsd-stable@pobox.com>, FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: vt(4) and geli(8) Message-ID: <273B57D9-65AB-4781-87A6-C8F980F81587@gmail.com> In-Reply-To: <CAGE5yCrJ-%2BKdH9%2BpPhsObrh6si-w%2BOMQFL04hU_BrsGJZrDdow@mail.gmail.com> References: <alpine.BSF.2.00.1404181026430.12069@roadkill.tharned.org> <5351CEF6.3060007@pobox.com> <CAGE5yCrJ-%2BKdH9%2BpPhsObrh6si-w%2BOMQFL04hU_BrsGJZrDdow@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 18, 2014, at 8:10 PM, Peter Wemm <peter@wemm.org> wrote: > On Fri, Apr 18, 2014 at 6:18 PM, Chris Nehren > <cnehren+freebsd-stable@pobox.com> wrote: >> On 2014/04/18, 11:36, Greg Rivers wrote: >>>=20 >>> The new vt system console looks really nice. But on hosts that >>> have geli encrypted devices that prompt for the passphrase at >>> boot, no keyboard input reaches geli. The keyboard doesn't >>> appear to be dead, as the caps-lock and num-lock keys toggle; >>> geli just doesn't receive any input. This is on 10-STABLE amd64 >>> built from yesterday's sources. "hw.vga.textmode=3D1" doesn't make >>> any difference. >>>=20 >>> Has anyone else encountered this? >>>=20 >>=20 >> Yes, I have, on my FreeBSD workstation with a USB keyboard. It's = running >> FreeBSD 10 with geli-encrypted ZFS root. This happened before I = updated to >> vt, though. I managed to work around the problem, surprisingly = enough, by >> mashing the keyboard when the system boots as soon as I see bold = white >> kernel text. Then, when prompted for the passphrase (after all the = USB >> devices finish probing / attaching), I hit enter to clear the buffer = and >> then am able to enter the passphrase correctly. >>=20 >> I'll be filing a PR for this, probably on Monday, should I not be = able to >> find one that's similar. >>=20 >> -- >> Chris Nehren >=20 > For what it's worth, I don't think this is specific to vt. You can > sometimes get the same behavior when you hit the mountroot prompt. > Some of the machines in the freebsd cluster will accept input at a > mountroot prompt, the others we have to power cycle and fix > vfs.root.mountfrom. vt isn't involved. I don't know what the > variable is. >=20 > I once suspected it is some combination of ddb/kdb presence, and/or > serial console / multiconsole mode but I don't think that holds up. I fixed this bug on SERIAL consoles by making the grab/ungrab function shift the serial port from interrupt driven processing to polled = processing. Maybe a similar change is now needed for atkbd? Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?273B57D9-65AB-4781-87A6-C8F980F81587>