From owner-freebsd-current@freebsd.org Thu Mar 30 07:40:36 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 C78DFD2506F for ; Thu, 30 Mar 2017 07:40:36 +0000 (UTC) (envelope-from mailing-machine@vniz.net) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id A61348F1 for ; Thu, 30 Mar 2017 07:40:36 +0000 (UTC) (envelope-from mailing-machine@vniz.net) Received: by mailman.ysv.freebsd.org (Postfix) id A297BD2506E; Thu, 30 Mar 2017 07:40:36 +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 A234CD2506D for ; Thu, 30 Mar 2017 07:40:36 +0000 (UTC) (envelope-from mailing-machine@vniz.net) Received: from mail-lf0-f67.google.com (mail-lf0-f67.google.com [209.85.215.67]) (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 316368EE for ; Thu, 30 Mar 2017 07:40:35 +0000 (UTC) (envelope-from mailing-machine@vniz.net) Received: by mail-lf0-f67.google.com with SMTP id n78so3777465lfi.3 for ; Thu, 30 Mar 2017 00:40:35 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=DDuMHch/QfkzblMB2YR6U8jlq1L/esjHbPclZQhlBYQ=; b=Z+fJL1m4prSQ3lFXqeO/QW0RGmOVPviaMXfF7/WGhlcjf1TrswIOurMOMWHVZT8gCy 649EgnNRnKxfXuemjuEX0Y5T27B2PFT0O+Ht0e+tEiLW5Mb1Apa4XJ3RRS00bWvKL8b/ rcT2DRyFEXoISCzILfvEXzW2NHqzT86FDXKmt92Yqwka1/XHwcXqFVPqrf6m9+JRmG8i hlbHpqYphV4neT8thXhRxnL3VgSwdVjnOwz83qOplCz7XLWgw4377Zy5BOiN6ZmEj1ec wuaki/pSvi5+STp9dt78aSgLhGStzqLHRwl0oS1xKPlHyFYaobAzTwmGnoLbllOSHmNE WW/w== X-Gm-Message-State: AFeK/H08UnUXoZrO2LmCHFAuVe00y+wC7iivXsGxpZ5JBmpUjUBMaNwblcRq+3ZP/wCDnQ== X-Received: by 10.46.32.152 with SMTP id g24mr1449805lji.78.1490859633412; Thu, 30 Mar 2017 00:40:33 -0700 (PDT) Received: from [192.168.1.2] ([89.169.173.68]) by smtp.gmail.com with ESMTPSA id e2sm219437ljb.9.2017.03.30.00.40.32 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 30 Mar 2017 00:40:32 -0700 (PDT) Subject: Re: New syscons bugs: shutdown -r doesn't execute rc.d sequence and others To: Bruce Evans 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> <20170330150449.R1061@besplex.bde.org> <3534bbeb-9f73-4e37-8f89-c05dd9f89f8c@freebsd.org> Cc: "Ngie Cooper (yaneurabeya)" , bde@freebsd.org, current@freebsd.org From: Andrey Chernov Message-ID: <74ff3f3b-3001-4bdd-1c4b-251a2c4a6f90@freebsd.org> Date: Thu, 30 Mar 2017 10:40:31 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <3534bbeb-9f73-4e37-8f89-c05dd9f89f8c@freebsd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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: Thu, 30 Mar 2017 07:40:36 -0000 On 30.03.2017 9:51, Andrey Chernov wrote: > On 30.03.2017 8:53, Bruce Evans wrote: >>> Maybe two will be enough too, I don't check. I just don't need _any_ of >>> vt lines. What is matter it is that syscons only mode (without any vt) >>> was recently broken, causing shutdown problems and file system damage >>> each time. Syscons only mode works for years until you break it recently. >> >> Actually, I fixed it not so recently (over the last few months), partly >> with much older local fixes. > > Please commit your fix as soon as possible. vt is broken as designed in > many aspects (I even mention not all of them), but from other hand I > can't allow dirty filesystem (or hang) on each reboot using sc only mode > as always. It is dangerous, and fsck takes big time. Moreover, using sc > while keeping vt bloat compiled in the kernel just as the bug workaround > is the best demotivator for perfectionist. > >> The escape sequences in dmesg are very interesting. You should debug >> those. > > I'll send you them a bit later. Since I don't want vt at all, I don't > want to debug or fix it, let it die. Here it is: kernel: allscreens_kbd cursor^[[=0A^[[=7F^[[=0G^[[=0H^[[=7Ividcontrol: setting cursor type: Inappropriate ioctl for device It is caused by vidcontrol call which left from previous sc setup. >>> I'll try. thanx. But most dangerous new syscons bug is the first one, >>> damaging file system on each reboot. I try to go to KDB to debug it, but >>> seeing that I can't even enter KDB I understand that all that bugs, >>> including nasty one, are introduced by your syscons changes, it was a >>> hint to add completely unneeded and unused vt to my kernel config file. >> >> It's normal to have a slightly damaged file system after a panic. > > In sc only mode I have no kernel panic, i.e panic with trace on console > or entering KDB. I have silent reboot in the middle or end of shutdown > sequence or rare dead hang on reboot (which absolutely not acceptable > for remote machine). > >> You might have entered ddb in a context which used to race or deadlock. > > No. I try about 20 times on machine which does nothing and can't enter > KDB in sc only mode, but got one dead hang instead, when start to repeat > it too fast. In vt mode I can enter each time, but there are exit > problems I already mention. > I use text mode in sc. > >> Strings for function keys: >> - these are just broken in both sc and vt > > I have all function keys working in sc only mode with TERM=cons25 and > similar ones. > >> Pseudographics: >> - I don't use it enough to see problems in it. Even finding the unicode >> glyph for the block character took me some time. > > Even cp437 have it and dialog library use it for all windows frames, > f.e. all ports config windows use pseudographics if it is available and > working (replaced by +-| etc poor looking ASCII otherwise).