From owner-freebsd-current@freebsd.org Fri Mar 31 03:21:58 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 0897BD23EDB for ; Fri, 31 Mar 2017 03:21:58 +0000 (UTC) (envelope-from mailing-machine@vniz.net) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id D7E2A964 for ; Fri, 31 Mar 2017 03:21:57 +0000 (UTC) (envelope-from mailing-machine@vniz.net) Received: by mailman.ysv.freebsd.org (Postfix) id D7078D23EDA; Fri, 31 Mar 2017 03:21:57 +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 D68F9D23ED9 for ; Fri, 31 Mar 2017 03:21:57 +0000 (UTC) (envelope-from mailing-machine@vniz.net) Received: from mail-lf0-f66.google.com (mail-lf0-f66.google.com [209.85.215.66]) (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 62506961 for ; Fri, 31 Mar 2017 03:21:56 +0000 (UTC) (envelope-from mailing-machine@vniz.net) Received: by mail-lf0-f66.google.com with SMTP id r36so6173606lfi.0 for ; Thu, 30 Mar 2017 20:21:56 -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=gt9FRnMVHKtALAxNJTK/x0svqT+rN8vQszB4kRjcK5g=; b=eK/MV9dhJwTKr9gpyvm9xEUE2ebXq4rl5feJqR+2LcMAiF8uEKmGE7A0Y5MlrIF9xx 1nQdk4A4HyCqcPFa4rYs7ddRimWXCsh2Q/h22wXWX7s+cMI9Mu5L0uBav8TAMO0iQfz9 0fw94WGk142FWvZau5ebGfgg5l/CuoiEe3X2Am0kfcbMam95MHwbRxML0bYWvyksR/9u ie2hRTXhS9TPDm1xN9Obj+7vKW2pwMgzSHh6nf0W1F2Rl7umL8rTyPf5RRmV+IE3CMDE 4hFLxc/uA1oSD7ejATqDXE35t3kCDHJOVZd6TFs6n1maJkT+Fa8JGTYMrgVsSYzhT49V KBYA== X-Gm-Message-State: AFeK/H2VeeWr+v4wxi/ZXqQgHN26unwqZc5l90KAGj/zYCpdkQjzhiizjBBSsJ2Mmq00Sg== X-Received: by 10.46.87.13 with SMTP id l13mr212904ljb.85.1490930514646; Thu, 30 Mar 2017 20:21:54 -0700 (PDT) Received: from [192.168.1.2] ([89.169.173.68]) by smtp.gmail.com with ESMTPSA id f187sm673916lfg.37.2017.03.30.20.21.53 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 30 Mar 2017 20:21:54 -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> <20170330183716.W1655@besplex.bde.org> <4085b441-74ee-796f-adc0-713dfc198b03@freebsd.org> <1772f54a-4268-577a-8e7f-abce929d39c8@freebsd.org> <20170331015718.X3330@besplex.bde.org> <20170331042950.F840@besplex.bde.org> Cc: "Ngie Cooper (yaneurabeya)" , avg@freebsd.org, bde@freebsd.org, current@freebsd.org From: Andrey Chernov Message-ID: <6258c93b-3771-887a-0c35-4286b2f63dbd@freebsd.org> Date: Fri, 31 Mar 2017 06:21:52 +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: <20170331042950.F840@besplex.bde.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: Fri, 31 Mar 2017 03:21:58 -0000 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?