Hello.
With the commit of r335510 releng/11.2 switched to -RELEASE. So I
updated one of my home server from 11.1-RELEASE-p11 to 11.2-RELEASE.
But when I rebooted I found OS boot messages are not displayed on
console while OS itself has booted successfully. To be exact,
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.
Kernel configuration is as follwing.
----------------------------------------------------------------------
yasu at maybe[2006]% uname -a
~
FreeBSD maybe.home.utahime.org 11.2-RELEASE FreeBSD 11.2-RELEASE #0 r335513: Fri
Jun 22 16:12:12 JST 2018 rootz at
maybe.home.utahime.org:/usr0/freebsd/base/obj/usr0/freebsd/base/releng/11.2/sys/MAYBE
amd64
yasu at maybe[2007]% cat /usr/src/sys/amd64/conf/MAYBE
~
#
# MAYBE -- Local kernel configuration file of maybe for FreeBSD/amd64
#
# For more information on this file, please read the config(5) manual page,
# and/or the handbook section on Kernel Configuration Files:
#
#
http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html
#
# The handbook is also available locally in /usr/share/doc/handbook
# if you've installed the doc distribution, otherwise always see the
# FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the
# latest information.
#
# An exhaustive list of options and more detailed explanations of the
# device lines is also present in the ../../conf/NOTES and NOTES files.
# If you are in doubt as to the purpose or necessity of a line, check first
# in NOTES.
#
# $FreeBSD$
include GENERIC
ident MAYBE
# ZFS support
options ZFS
# PF support
device pf #PF OpenBSD packet-filter firewall
device pflog #logging support interface for PF
#
# Temperature sensors:
#
# coretemp: on-die sensor on Intel Core and newer CPUs
#
device coretemp
yasu at maybe[2008]%
----------------------------------------------------------------------
I tried GENERIC kernel but the problem still happened.
HWs are,
M/B: ASUS N3150I-C
(https://www.asus.com/us/Motherboards/N3150IC/)
Display: EIZO FlexScan L565
(http://www.eizoglobal.com/support/db/products/model/L565)
M/B and display are connected with analog VGA.
Does anyone experiences same problem? Are there any solution or
workaound?
Best Regards.
---
Yasuhiro KIMURA
On 22.06.2018 11:07, Yasuhiro KIMURA wrote:> Hello. > > With the commit of r335510 releng/11.2 switched to -RELEASE. So I > updated one of my home server from 11.1-RELEASE-p11 to 11.2-RELEASE. > > But when I rebooted I found OS boot messages are not displayed on > console while OS itself has booted successfully. To be exact, > > 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.Do you have some tweaks for serial console in your loader.conf? -- WBR, Andrey V. Elsukov -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 553 bytes Desc: OpenPGP digital signature URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20180622/1f206c2c/attachment.sig>
From: Yasuhiro KIMURA <yasu at utahime.org> Subject: Console is broken after updating to 11.2-RELEASE Date: Fri, 22 Jun 2018 17:07:20 +0900 (JST)> With the commit of r335510 releng/11.2 switched to -RELEASE. So I > updated one of my home server from 11.1-RELEASE-p11 to 11.2-RELEASE. > > But when I rebooted I found OS boot messages are not displayed on > console while OS itself has booted successfully. To be exact, > > 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 have another 11.1-RELEASE-p11 amd64 environment working as guest of VirtualBox whose host is 64bit Windows 10. So I updated it to 11.2-RELEASE like my home server in question. But in this case console worked fine just as it was 11.1-RELEASE-p11. So the problem seems to be hardwear dependent. --- Yasuhiro KIMURA
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.
UEFI or legacy boot? Is a BMC involved? Warner On Fri, Jun 22, 2018, 2:09 AM Yasuhiro KIMURA <yasu at utahime.org> wrote:> Hello. > > With the commit of r335510 releng/11.2 switched to -RELEASE. So I > updated one of my home server from 11.1-RELEASE-p11 to 11.2-RELEASE. > > But when I rebooted I found OS boot messages are not displayed on > console while OS itself has booted successfully. To be exact, > > 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. > > Kernel configuration is as follwing. > > ---------------------------------------------------------------------- > yasu at maybe[2006]% uname -a > ~ > FreeBSD maybe.home.utahime.org 11.2-RELEASE FreeBSD 11.2-RELEASE #0 > r335513: Fri Jun 22 16:12:12 JST 2018 rootz at maybe.home.utahime.org:/usr0/freebsd/base/obj/usr0/freebsd/base/releng/11.2/sys/MAYBE > amd64 > yasu at maybe[2007]% cat /usr/src/sys/amd64/conf/MAYBE > ~ > # > # MAYBE -- Local kernel configuration file of maybe for FreeBSD/amd64 > # > # For more information on this file, please read the config(5) manual page, > # and/or the handbook section on Kernel Configuration Files: > # > # > http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html > # > # The handbook is also available locally in /usr/share/doc/handbook > # if you've installed the doc distribution, otherwise always see the > # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the > # latest information. > # > # An exhaustive list of options and more detailed explanations of the > # device lines is also present in the ../../conf/NOTES and NOTES files. > # If you are in doubt as to the purpose or necessity of a line, check first > # in NOTES. > # > # $FreeBSD$ > > include GENERIC > > ident MAYBE > > # ZFS support > options ZFS > > # PF support > device pf #PF OpenBSD packet-filter firewall > device pflog #logging support interface for PF > > # > # Temperature sensors: > # > # coretemp: on-die sensor on Intel Core and newer CPUs > # > device coretemp > yasu at maybe[2008]% > ---------------------------------------------------------------------- > > I tried GENERIC kernel but the problem still happened. > > HWs are, > > M/B: ASUS N3150I-C > (https://www.asus.com/us/Motherboards/N3150IC/) > Display: EIZO FlexScan L565 > (http://www.eizoglobal.com/support/db/products/model/L565) > > M/B and display are connected with analog VGA. > > Does anyone experiences same problem? Are there any solution or > workaound? > > Best Regards. > > --- > Yasuhiro KIMURA > _______________________________________________ > freebsd-stable at freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org" >
I submitted this problem as following bug report. Bug 229235 - vt(4) of 11.2-RELEASE is broken with hardware dependent problem. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229235 Just FYI. --- Yasuhiro KIMURA