From owner-freebsd-current@freebsd.org Wed Mar 29 06:24:08 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 9158BD237AD for ; Wed, 29 Mar 2017 06:24:08 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 6C23B67D2B for ; Wed, 29 Mar 2017 06:24:08 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 68AE8D237AC; Wed, 29 Mar 2017 06:24:08 +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 66A00D237AB for ; Wed, 29 Mar 2017 06:24:08 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-pf0-x244.google.com (mail-pf0-x244.google.com [IPv6:2607:f8b0:400e:c00::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2967967D29; Wed, 29 Mar 2017 06:24:08 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: by mail-pf0-x244.google.com with SMTP id r137so703674pfr.3; Tue, 28 Mar 2017 23:24:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=jab9tnx4c7vtbnip6gmI5xFQVCrLx40wMJPwYkYkkgc=; b=LncnAiIMwj5Ml63ShNmk9L1nZbb8lbPOKf5+lvFNU9E641qs9jK+KakxfJiPG9s2yB bJcsRICZ1rwhrgGRpAnG9zNn5jbyhvrJyufum+T91t3cJOWBUvj/XNk18KfVAlF8xV90 OuAsLuQL5HkbOLuBk1hR+ut++wD1Zd8zEb2kT0CasotpG6N0Ke9Cjk4mYkX5diU4hxO4 GViaGemsrJXfmROZ6Ea3lXl9mgHjy7shcdCI/ro3Ub9fmcIjie2AOq8bjJkMZhRxz3F+ 5DA1xcPIaIBOWiscR8fypgYJNz3qO2upsW6u/9YoV6oJUG8FWDy49she87fQBgKBJ1Nw HDQA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=jab9tnx4c7vtbnip6gmI5xFQVCrLx40wMJPwYkYkkgc=; b=ggXWUu3wZU4o2Gtlc0pGXXgg/yG8WXo1lQPWkzSSdDoQNxIkLBnvrnmaly+8nund7c 45VWfY2rkBd7s+tRyzWa5JP9qQLrQdWyw/3Bb5bULhUr2u99BB0gWd9ko8El2IyLsNlU TxdH78xffSqbhLY89J3YOAc0eWZaQnJkQY+I0EG1ncsropcVpVKTSYEJ9z9B09sB5y6A dPk4ue6K/NrNonpJY3EZrhflZNjyDLGW0pdF2GmW7BcROOgxdrUpZQUag1yQFrNY1DqO FptX0McvpkWag9iUciwInY6cGRPkdwIC5trOKkl71a7aPOAukMJ62puJxvuHFhZaBFi5 eBJw== X-Gm-Message-State: AFeK/H0S741DE+Xvgtjqso5WwFbM8zcKec8bdenaBaxKDcoAPK3iqYxyPVcC2yvcNCsW2A== X-Received: by 10.98.139.78 with SMTP id j75mr34668593pfe.122.1490768647544; Tue, 28 Mar 2017 23:24:07 -0700 (PDT) Received: from ?IPv6:2607:fb90:8350:9a20:47c:5ab4:774e:ed5c? ([2607:fb90:8350:9a20:47c:5ab4:774e:ed5c]) by smtp.gmail.com with ESMTPSA id x15sm10935187pgc.16.2017.03.28.23.24.06 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 28 Mar 2017 23:24:06 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: New syscons bugs: shutdown -r doesn't execute rc.d sequence and others From: Ngie Cooper X-Mailer: iPhone Mail (14D27) In-Reply-To: <20170329150903.T1156@besplex.bde.org> Date: Tue, 28 Mar 2017 23:24:05 -0700 Cc: Andrey Chernov , bde@freebsd.org, current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <8078CD32-2DFB-4296-BD92-29627A1B4559@gmail.com> 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> To: Bruce Evans 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 06:24:08 -0000 > On Mar 28, 2017, at 21:40, Bruce Evans wrote: >=20 >> On Wed, 29 Mar 2017, Bruce Evans wrote: >>=20 >>> 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. >>=20 >> ... >> 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. >>=20 >> 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. >=20 > I tested usb keyboards again. They sometimes work, much the same as > a few months ago after some fixes: > - after booting with -d, they never work (give no input) at the ddb > prompt with either sc or vt. usb is not initialized then, and no usb > keyboard is attached to sc or vt > - after booting without loader with -a, sc rarely or never works (gives > no input) at the mountroot prompt > - after booting with loader with -a, vt works at the mountroot prompt. > I don't normally use loader but need to use it to change the configuratio= n. > This might be better than before. There used to be a screen refresh bug.= > - after booting with loader with -a, sc works at the mountroot prompt too.= > I previously debugged that vt worked better because it attaches the keybo= ard > before this point, while sc attaches it after. Booting with loader > apparently fixes the order. > - after any booting, sc works for user input (except sometimes after a > too-soft hard reset, the keyboard doesn't even work in the BIOS, and it > takes unplugging the keyboard to fix this) > - after almost any booting, vt doesn't work for user input (gives no input= ). > However, if ddb is entered using a serial console, vt does work! A few > months ago, normal input was fixed by configuring kbdmux (the default in > GENERIC). It is not fixed by unplugging the keyboard. kbdmux has a know= n > bug of not doing nested switching for the keyboard state. Perhaps this > "fixes" ddb mode. But I would have expected it to break ddb mode. > - I didn't test sc after entering ddb, except early when it doesn't work. >=20 > 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 y= ou increase the timeout so the USB hubs have enough time to probe/attach, th= ey will work. I haven't taken the time to follow up on that and fix the issue, or at least= propose a bit more functional workaround. HTH, -Ngie=