From owner-freebsd-current@freebsd.org Wed Mar 29 08:26:27 2017 Return-Path: Delivered-To: freebsd-current@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 A0579D2251D for ; Wed, 29 Mar 2017 08:26:27 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 893E76BBB6 for ; Wed, 29 Mar 2017 08:26:27 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: by mailman.ysv.freebsd.org (Postfix) id 85A77D2251C; Wed, 29 Mar 2017 08:26:27 +0000 (UTC) Delivered-To: current@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 8542FD2251B for ; Wed, 29 Mar 2017 08:26:27 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from mail108.syd.optusnet.com.au (mail108.syd.optusnet.com.au [211.29.132.59]) by mx1.freebsd.org (Postfix) with ESMTP id 43C176BBB5; Wed, 29 Mar 2017 08:26:26 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from besplex.bde.org (c122-106-153-191.carlnfd1.nsw.optusnet.com.au [122.106.153.191]) by mail108.syd.optusnet.com.au (Postfix) with ESMTPS id 6D0191A4244; Wed, 29 Mar 2017 19:26:24 +1100 (AEDT) Date: Wed, 29 Mar 2017 19:26:23 +1100 (EST) From: Bruce Evans X-X-Sender: bde@besplex.bde.org To: Ngie Cooper cc: Bruce Evans , Andrey Chernov , bde@freebsd.org, current@freebsd.org Subject: Re: New syscons bugs: shutdown -r doesn't execute rc.d sequence and others In-Reply-To: <8078CD32-2DFB-4296-BD92-29627A1B4559@gmail.com> Message-ID: <20170329190919.C26218@besplex.bde.org> References: <7d5bbbf0-6908-185c-2ee0-29e0a4f60591@freebsd.org> <5587c798-d36c-9074-1060-30e206db5571@freebsd.org> <69af07a7-ec8f-9b7f-8b93-9ba148f30fec@freebsd.org> <8C24D1BA-1607-4C19-BA38-39256E82C7AF@gmail.com> <51045bee-a626-efb3-4b1e-0c3d36abb1ab@freebsd.org> <20170329132927.U882@besplex.bde.org> <20170329150903.T1156@besplex.bde.org> <8078CD32-2DFB-4296-BD92-29627A1B4559@gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Optus-CM-Score: 0 X-Optus-CM-Analysis: v=2.2 cv=VbSHBBh9 c=1 sm=1 tr=0 a=Tj3pCpwHnMupdyZSltBt7Q==:117 a=Tj3pCpwHnMupdyZSltBt7Q==:17 a=kj9zAlcOel0A:10 a=PO7r1zJSAAAA:8 a=djocrBDfS-jKbYuDqNYA:9 a=CjuIK1q_8ugA:10 a=Oa0T6EYmKFNB-xRHvYM1:22 X-Mailman-Approved-At: Wed, 29 Mar 2017 11:40:04 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Mar 2017 08:26:27 -0000 On Tue, 28 Mar 2017, Ngie Cooper wrote: >> On Mar 28, 2017, at 21:40, Bruce Evans wrote: >> >>> On Wed, 29 Mar 2017, Bruce Evans wrote: >>> >>>> On Wed, 29 Mar 2017, Andrey Chernov wrote: >>>> ... >>>> Moreover, I can't enter KDB via Ctrl-Alt-ESC in the syscons only mode >>>> anymore - nothing happens. In the vt mode I can, but can't exit via "c" >>>> properly, all chars typed after "c" produce beep unless I switch to >>>> another screen and back. >>>> All it means that syscons becomes very broken now by itself and even >>>> damages the kernel operations. I found a bug in screen resizing (the console context doesn't get resized). This doesn't cause any keyboard problems. >>> ... >>> But I suspect it is a usb keyboard problem. Syscons now does almost >>> correct locking for the screen, but not for the keyboard, and the usb >>> keyboard is especially fragile, especially in ddb mode. Console input >>> is not used in normal operation except for checking for characters on >>> reboot. >>> >>> Try using vt with syscons unconfigured. Syscons shouldn't be used when >>> vt is selected, but unconfigure it to be sure. vt has different bugs >>> using the usb keyboard. I haven't tested usb keyboards recently. >> >> ... >> I tested usb keyboards again. They sometimes work, much the same as >> a few months ago after some fixes: >> ... >> >> The above testing is with a usb keyboard, no ps/2 keyboard, and no kbdmux. >> Other combinations and dynamic switching move the bugs around, and a >> serial console is needed to recover in cases where the bugs prevent any >> keyboard input. > > I filed a bug a few years ago about USB keyboards and usability in ddb. If you increase the timeout so the USB hubs have enough time to probe/attach, they will work. Is that for user mode or earlier? ukb has some other fixes for ddb now, but of course it can't work before it finds the device. I recently found that usb boot drives sometimes don't have enough time to probe/attach before they are used in mountroot, and the mount -a prompt does locking that doesn't allow them enough time if they are not ready before it. The usb maintainers already know about this. > I haven't taken the time to follow up on that and fix the issue, or at least propose a bit more functional workaround. Bruce