Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 31 Mar 2017 06:21:52 +0300
From:      Andrey Chernov <ache@freebsd.org>
To:        Bruce Evans <brde@optusnet.com.au>
Cc:        "Ngie Cooper (yaneurabeya)" <yaneurabeya@gmail.com>, avg@freebsd.org, bde@freebsd.org, current@freebsd.org
Subject:   Re: New syscons bugs: shutdown -r doesn't execute rc.d sequence and others
Message-ID:  <6258c93b-3771-887a-0c35-4286b2f63dbd@freebsd.org>
In-Reply-To: <20170331042950.F840@besplex.bde.org>
References:  <7d5bbbf0-6908-185c-2ee0-29e0a4f60591@freebsd.org> <D9EAB41D-CE19-4225-8868-F4AFE461F903@gmail.com> <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> <f35b6ae1-c668-0649-e327-f57811b1d71a@freebsd.org> <20170330150449.R1061@besplex.bde.org> <3534bbeb-9f73-4e37-8f89-c05dd9f89f8c@freebsd.org> <20170330183716.W1655@besplex.bde.org> <4085b441-74ee-796f-adc0-713dfc198b03@freebsd.org> <1772f54a-4268-577a-8e7f-abce929d39c8@freebsd.org> <e4b3dd02-6dd2-0723-eed1-a3fd0be5b651@freebsd.org> <20170331015718.X3330@besplex.bde.org> <e1830cff-58af-f0b1-bab9-935ba32883f4@freebsd.org> <20170331042950.F840@besplex.bde.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 30.03.2017 21:53, Bruce Evans wrote:
> I think it was the sizing.  The non-updated mode is 80x25, so the row
> address can be out of bounds in the teken layer.

I have text 80x30 mode set at rc stage, and _after_ that may have many
kernel messages on console, all without causing reboot. How it is
different from shutdown stage? Syscons mode is unchanged since rc stage.

> - sysctl debug.kdb.break_to_debugger.  This is documented in ddb(4), but
>   only as equivalent to the unbroken BREAK_TO_DEBUGGER.

Thanx. Setting debug.kdb.break_to_debugger=1 makes both Ctrl-Alt-ESC and
Ctrl-PrtScr works in sc only mode and "c" exit don't cause all chars
beeps like in vt. I.e. it works. But I don't understand why debugging
via serial involved in sc case while not involved in vt case and fear
that some serial noise may provoke break. Is there a chance to untie
serial and sc console debuggers?




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6258c93b-3771-887a-0c35-4286b2f63dbd>