From owner-freebsd-amd64@freebsd.org Mon Aug 15 22:45:06 2016 Return-Path: Delivered-To: freebsd-amd64@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1465EBB9A57 for ; Mon, 15 Aug 2016 22:45:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id ED7221C03 for ; Mon, 15 Aug 2016 22:45:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u7FMj5pO094824 for ; Mon, 15 Aug 2016 22:45:05 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-amd64@FreeBSD.org Subject: [Bug 211884] IPKVM cannot reliably enter text under 11.0-RC2 Date: Mon, 15 Aug 2016 22:45:05 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-RC1 X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: karl@denninger.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter cc Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-Mailman-Approved-At: Mon, 15 Aug 2016 23:14:08 +0000 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Aug 2016 22:45:06 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211884 Bug ID: 211884 Summary: IPKVM cannot reliably enter text under 11.0-RC2 Product: Base System Version: 11.0-RC1 Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: karl@denninger.net CC: freebsd-amd64@FreeBSD.org CC: freebsd-amd64@FreeBSD.org Updated from 11.0-ALPHA to 11.0-RC2 this afternoon on a test machine and ran into a really odd problem. The system in question has an encrypted root ZFS pool, which results in a prompt for the GELI password during the boot and before the root filesystem mounts. This has been trouble-free for a long time. This afternoon, however, it suddenly turned into a huge problem. After the kernel loads and the prompt comes up the keyboard was not recognized over t= he IPMI interface; only one of every handful of keystrokes went through. This meant if you pounded the enter key a few times you'd eventually get one through, but the keys you typed in the meantime (containing the GELI passwo= rd!) were of course lost - or some of them were anyway. A locally-attached PS/2 keyboard (at the physical machine) works, but a USB-attached keyboard *also* had intermittent problems, often NOT registeri= ng the CAPS and NUMLOCK keys reliably. The IPMI keyboard is recognized properly at the BIOS level (before the load= er gets control) and works fine there. This is likely to be extremely serious for anyone who attempts to update a system with encrypted disks over a remote link using a built-in IPKVM; the machine in question has a SuperMicro board in it, but given that I *also* h= ad trouble with a USB plugged keyboard on the same machine (but not a PS/2 keyboard!) it appears that this is something in the kernel level and *not* strictly an IPKVM interaction issue. Reverting to the previous ALPHA kernel resolved the problem immediately. In addition if I change the mouse mode on the web interface (which forces a detach/reattach for the keyboard, which I can see on the KVM console) it wi= ll *sometimes* permit me to type the password. IMHO this needs to be investigated as if RELEASE goes out with this problem present it is likely to screw a large number of people who are doing the upgrade remotely, possibly forcing a trip to the site with a physical keybo= ard to get beyond the prompt. I do not know if this was a problem on RC1 as I didn't run it but it was NO= T an issue in the ALPHA series of releases. --=20 You are receiving this mail because: You are on the CC list for the bug.=