From owner-freebsd-stable@freebsd.org  Fri Jun 22 11:43:51 2018
Return-Path: <owner-freebsd-stable@freebsd.org>
Delivered-To: freebsd-stable@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 82C961018490
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Fri, 22 Jun 2018 11:43:51 +0000 (UTC)
 (envelope-from yasu@utahime.org)
Received: from gate.utahime.jp (ipq210.utahime.jp [183.180.29.210])
 by mx1.freebsd.org (Postfix) with ESMTP id 049CC8CEF6
 for <freebsd-stable@FreeBSD.org>; Fri, 22 Jun 2018 11:43:50 +0000 (UTC)
 (envelope-from yasu@utahime.org)
Received: from eastasia.home.utahime.org (eastasia.home.utahime.org
 [192.168.174.1])
 by gate.utahime.jp (Postfix) with ESMTP id F3DCC18043;
 Fri, 22 Jun 2018 20:43:46 +0900 (JST)
Received: from eastasia.home.utahime.org (localhost [127.0.0.1])
 by localhost-backdoor.home.utahime.org (Postfix) with ESMTP id CB1C7162B6;
 Fri, 22 Jun 2018 20:43:46 +0900 (JST)
Received: from localhost (rolling.home.utahime.org [192.168.174.11])
 by eastasia.home.utahime.org (Postfix) with ESMTPSA id AB7ED162B5;
 Fri, 22 Jun 2018 20:43:46 +0900 (JST)
Date: Fri, 22 Jun 2018 20:43:28 +0900 (JST)
Message-Id: <20180622.204328.2245607503460205311.yasu@utahime.org>
To: freebsd-stable@FreeBSD.org
Subject: Re: Console is broken after updating to 11.2-RELEASE
From: Yasuhiro KIMURA <yasu@utahime.org>
In-Reply-To: <af667f73-8b08-27a4-8c4b-2dc8db7401f8@zyxst.net>
References: <20180622.170720.1809136341323718366.yasu@utahime.org>
 <af667f73-8b08-27a4-8c4b-2dc8db7401f8@zyxst.net>
X-Mailer: Mew version 6.8 on Emacs 26.1
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2018 11:43:51 -0000

From: tech-lists <tech-lists@zyxst.net>
Subject: Re: Console is broken after updating to 11.2-RELEASE
Date: Fri, 22 Jun 2018 11:44:29 +0100

> I've seen this effect elsewhere. Not exactly the same, but it's been
> happening with me on some systems since 11.1. The context I see it is
> when spinning up a bhyve instance in screen. I see a bit more than
> just booting, something like "unreferenced ps/2 interrupt" after
> "Booting...".
> 
> The bhyve instance itself is fully functional. Logging into the bhyve
> instance through ssh I can see its dmesg and it all looks OK. However,
> if in syslogd.conf I enable console logging via console.log and
> reboot, *nothing gets written to it*.

Thank you for information. I created /etc/syslog.d/console.log.conf as
below and rebooted system.

yasu@maybe[2012]% cat /etc/syslog.d/console.log.conf                                                                       ~
# Log all writes to /dev/console to a separate file.
!*
console.*                                       /var/log/console.log
!*
yasu@maybe[2013]%

Then boot messages are written in /var/log/console.log

yasu@maybe[2016]% LANG=C ls -l /var/log/console.log                                                                        ~
-rw-r--r--  1 root  wheel  9568 Jun 22 20:29 /var/log/console.log
yasu@maybe[2016]%

So my case seems to be different from yours.

---
Yasuhiro KIMURA