From owner-freebsd-stable@FreeBSD.ORG Sat Apr 19 02:10:58 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 082066B6 for ; Sat, 19 Apr 2014 02:10:58 +0000 (UTC) Received: from mail-ve0-x234.google.com (mail-ve0-x234.google.com [IPv6:2607:f8b0:400c:c01::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B604D19FD for ; Sat, 19 Apr 2014 02:10:57 +0000 (UTC) Received: by mail-ve0-f180.google.com with SMTP id jz11so4025299veb.39 for ; Fri, 18 Apr 2014 19:10:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wemm.org; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=iKOO/+kZRJM5eaUPp6Myhbo58r2LjHnuFH3e7DzSL5c=; b=ByRFdzWjIn1yTnN4QY7V6yN/hLLYoAhB2OqX7Dzu/mHv5a79ioXefxG/R/PIGO6Zxj SD6NJat442/wGqX8+7ngzptPDf20vehXQtAZPgSobUt3R4UELwCatMf9OPFbTy17lCos imf6l5p74F7k3lRGWZ8/1muQDWV0smXes+G20= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=iKOO/+kZRJM5eaUPp6Myhbo58r2LjHnuFH3e7DzSL5c=; b=TzbhnCxoePE7sOCNNeIGC+5EKqqw9XFj5j0F6TCQzkRqmHd4zbXq+BACtMh9Ue87pA l7SjA4Jeszi/vr9VYSH77AyOugeDd1v1O+DW4rkywbb+H8ktmssBsBM63S6fMxaeTAYk u+N06ohmeqm1ti+KnjznLKeb95ud2lBweRm5zWkkhfhkqcWmDLFr8E4AQpKHQs6hRnUk vpW8JxfD4sOqfUtuRraN5Uk3j0aEcloJoN2S1K2Lf39q4NDnS+Uv74IjRJ3Y4UDwBLrJ V9fOZFwxM9wbMFbM6BGv3YQASyntDrW23cr1gTP+U4eowV382r+0BcueGwksGoF3K2Pw uTSg== X-Gm-Message-State: ALoCoQlgf0+SVoj7+NkIs/a5H4VhMkCjpEbs5HpUeEEj/xO9ZH3Y15gbdf6MbH4TeQDPwRpmi/ec MIME-Version: 1.0 X-Received: by 10.58.1.5 with SMTP id 5mr20881695vei.8.1397873456379; Fri, 18 Apr 2014 19:10:56 -0700 (PDT) Received: by 10.220.30.69 with HTTP; Fri, 18 Apr 2014 19:10:56 -0700 (PDT) In-Reply-To: <5351CEF6.3060007@pobox.com> References: <5351CEF6.3060007@pobox.com> Date: Fri, 18 Apr 2014 19:10:56 -0700 Message-ID: Subject: Re: vt(4) and geli(8) From: Peter Wemm To: Chris Nehren Content-Type: text/plain; charset=UTF-8 Cc: 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:10:58 -0000 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=1" doesn't make >> any difference. >> >> Has anyone else encountered this? >> > > 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. > > I'll be filing a PR for this, probably on Monday, should I not be able to > find one that's similar. > > -- > Chris Nehren 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. 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. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com; KI6FJV