From owner-freebsd-stable@FreeBSD.ORG Sat Apr 19 02:35:51 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DE346B54; Sat, 19 Apr 2014 02:35:50 +0000 (UTC) Received: from mail0.glenbarber.us (mail0.glenbarber.us [208.86.227.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail0.glenbarber.us", Issuer "Gandi Standard SSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9569C1C25; Sat, 19 Apr 2014 02:35:50 +0000 (UTC) Received: from glenbarber.us (70.15.88.86.res-cmts.sewb.ptd.net [70.15.88.86]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by mail0.glenbarber.us (Postfix) with ESMTPSA id 09C1C12723; Sat, 19 Apr 2014 02:35:41 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.8.3 mail0.glenbarber.us 09C1C12723 Authentication-Results: mail0.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Fri, 18 Apr 2014 22:35:39 -0400 From: Glen Barber To: Peter Wemm Subject: Re: vt(4) and geli(8) Message-ID: <20140419023539.GO49791@glenbarber.us> References: <5351CEF6.3060007@pobox.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="B3NBd8mrXZtPJEYR" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event User-Agent: Mutt/1.5.23 (2014-03-12) Cc: Chris Nehren , FreeBSD Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Apr 2014 02:35:51 -0000 --B3NBd8mrXZtPJEYR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Apr 18, 2014 at 07:10:56PM -0700, Peter Wemm wrote: > On Fri, Apr 18, 2014 at 6:18 PM, Chris Nehren > wrote: > > On 2014/04/18, 11:36, Greg Rivers wrote: > >> > >> 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. > >> > >> Has anyone else encountered this? > >> > > > > Yes, I have, on my FreeBSD workstation with a USB keyboard. It's runni= ng > > FreeBSD 10 with geli-encrypted ZFS root. This happened before I update= d 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. > > > > I'll be filing a PR for this, probably on Monday, should I not be able = to > > find one that's similar. > > > > -- > > 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. >=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). 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. Glen --B3NBd8mrXZtPJEYR Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCAAGBQJTUeD7AAoJELls3eqvi17QL4wP/RTn+1Zw+FdFvGPXa5vT1Mn3 fQxJNLmjN0BclPIGpeBLuMjDCYNmO6f+Zg8g0EwRFrTjA6kbh30wNRckrledlTKd Z9D2rI7Lu7GCI4daq0tEJCfGhaP/DxLaSDA2O6mkfTc7J0lYvORYopqhp23AnBD4 jyuQeNSid0RYoxndNSfYYwuq1WyqtaTv5cpMNOcgE76LROLXcM0gn0m8G1HZRLeI LqEbxBH1Cu4mp68ldFqbXjiNYIQ2xyH2LUE+Le/vuHh2fYtRJ/+5f5VBUidMOGL2 H+csBlwGqDeQIb2XgDynUz2UEJS+5O52dtfoJ6Vka14Cmir2nd6x2iELQit/Fcg7 /RX0OGPQGq8RGp6jq8nzofvdDOxco+DjmaYWDLchpmrdGyGLYa5fzsxfk+NcCNrF IIY9a0iKmIreAiEBwcdTK80y1AXwPbnymkQa+V8gqSbG4Ze5KcJlOlfw7KQyzwcd ygs6qywIC52iChHV6ej9fTJRbH57naglXanW0rDKRhklVFMbJuTKnKrPJYkDHNx1 CnTY6QF/1SZtCdFIqeU3lXBC3hSv/KfG4uTI9Yt16lxzSdsbXVSl9eEVuM7gr1AV OR1nRdLTiIL7FHLWz7srdMA8WxQG/lJSKuVttiZjHWO99G5uvO5w7/TGz8N+h/ge Tp4BE7ul57V63Og6NGb7 =STTI -----END PGP SIGNATURE----- --B3NBd8mrXZtPJEYR--