Date: Fri, 22 Jun 2018 11:44:29 +0100 From: tech-lists <tech-lists@zyxst.net> To: Yasuhiro KIMURA <yasu@utahime.org>, freebsd-stable@FreeBSD.org Subject: Re: Console is broken after updating to 11.2-RELEASE Message-ID: <af667f73-8b08-27a4-8c4b-2dc8db7401f8@zyxst.net> In-Reply-To: <20180622.170720.1809136341323718366.yasu@utahime.org> References: <20180622.170720.1809136341323718366.yasu@utahime.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On 22/06/2018 09:07, Yasuhiro KIMURA wrote: > 1. BIOS message are displayed. > 2. Boot menu of FreeBSD is displayed. > 3. Kernel boot starts but after 'Booting...' no following messages > are displayed. > 4. After OS has booted console stays unusable. 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*. Have had this issue for about a year now, not been able to fix it. Frustratingly, it doesn't happen with all VMs. I've not seen it happen with a 12-current VM, just 11-stable. And even then, not *all* 11-stable VMs. -- J.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?af667f73-8b08-27a4-8c4b-2dc8db7401f8>