info
Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Console is broken after updating to 11.2-RELEASE
3 views
Skip to first unread message
Yasuhiro KIMURA
Jun 22, 2018, 4:11:46 AM6/22/18
to
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@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 ro...@maybe.home.utahime.org:/usr0/freebsd/base/obj/usr0/freebsd/base/releng/11.2/sys/MAYBE amd64
yasu@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@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...@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stabl...@freebsd.org"
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@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 ro...@maybe.home.utahime.org:/usr0/freebsd/base/obj/usr0/freebsd/base/releng/11.2/sys/MAYBE amd64
yasu@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@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...@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stabl...@freebsd.org"
Andrey V. Elsukov
Jun 22, 2018, 4:55:07 AM6/22/18
to
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?
> 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.
--
WBR, Andrey V. Elsukov
Yasuhiro KIMURA
Jun 22, 2018, 5:06:23 AM6/22/18
to
From: "Andrey V. Elsukov" <bu7...@yandex.ru>
Subject: Re: Console is broken after updating to 11.2-RELEASE,Re: Console is broken after updating to 11.2-RELEASE
Date: Fri, 22 Jun 2018 11:47:24 +0300
> Do you have some tweaks for serial console in your loader.conf?
No. I don't use serial console at all. Folloging is loader.conf of my
home server in question.
yasu@maybe[2019]% cat /boot/loader.conf
kern.geom.label.disk_ident.enable="0"
kern.geom.label.gptid.enable="0"
#zfs_load="YES"
yasu@maybe[2020]%
Subject: Re: Console is broken after updating to 11.2-RELEASE,Re: Console is broken after updating to 11.2-RELEASE
Date: Fri, 22 Jun 2018 11:47:24 +0300
> Do you have some tweaks for serial console in your loader.conf?
home server in question.
yasu@maybe[2019]% cat /boot/loader.conf
kern.geom.label.disk_ident.enable="0"
kern.geom.label.gptid.enable="0"
#zfs_load="YES"
yasu@maybe[2020]%
Yasuhiro KIMURA
Jun 22, 2018, 6:46:55 AM6/22/18
to
From: Yasuhiro KIMURA <ya...@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.
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.
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.
tech-lists
Jun 22, 2018, 6:49:55 AM6/22/18
to
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.
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.
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.
Warner Losh
Jun 22, 2018, 7:08:14 AM6/22/18
to
UEFI or legacy boot? Is a BMC involved?
Warner
Warner
Yasuhiro KIMURA
Jun 22, 2018, 7:47:49 AM6/22/18
to
From: tech-lists <tech-...@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
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*.
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
Yasuhiro KIMURA
Jun 22, 2018, 7:48:19 AM6/22/18
to
From: Warner Losh <i...@bsdimp.com>
> UEFI or legacy boot? Is a BMC involved?
Legacy boot. And BMC is not involved.
Subject: Re: Console is broken after updating to 11.2-RELEASE
Date: Fri, 22 Jun 2018 05:03:43 -0600
> UEFI or legacy boot? Is a BMC involved?
Chris H
Jun 22, 2018, 9:18:13 AM6/22/18
to
On Fri, 22 Jun 2018 20:42:18 +0900 (JST) "Yasuhiro KIMURA" <ya...@utahime.org> said
> From: Warner Losh <i...@bsdimp.com>
> Subject: Re: Console is broken after updating to 11.2-RELEASE
> Date: Fri, 22 Jun 2018 05:03:43 -0600
>
> > UEFI or legacy boot? Is a BMC involved?
>
> Legacy boot. And BMC is not involved.
Try adding the following to your loader.conf(5) file (/boot/loader.conf):
# Load SysCons driver
kern.vty=sc
# noisy boot
boot_verbose="YES"
Hope this helps!
--Chris
> From: Warner Losh <i...@bsdimp.com>
> Subject: Re: Console is broken after updating to 11.2-RELEASE
> Date: Fri, 22 Jun 2018 05:03:43 -0600
>
> > UEFI or legacy boot? Is a BMC involved?
>
> Legacy boot. And BMC is not involved.
# Load SysCons driver
kern.vty=sc
# noisy boot
boot_verbose="YES"
Hope this helps!
--Chris
Yasuhiro KIMURA
Jun 22, 2018, 2:01:39 PM6/22/18
to
From: "Chris H" <bsd-...@BSDforge.com>
> Try adding the following to your loader.conf(5) file
> (/boot/loader.conf):
>
> # Load SysCons driver
> kern.vty=sc
> # noisy boot
> boot_verbose="YES"
>
> Hope this helps!
Thank you for information. I added above lines to /boot/loader.conf
and rebooted system. Then all boot messages are displayed and console
works fine!
Subject: Re: Console is broken after updating to 11.2-RELEASE
Date: Fri, 22 Jun 2018 06:13:39 -0700
> Try adding the following to your loader.conf(5) file
> (/boot/loader.conf):
>
> # Load SysCons driver
> kern.vty=sc
> # noisy boot
> boot_verbose="YES"
>
> Hope this helps!
and rebooted system. Then all boot messages are displayed and console
works fine!
Yasuhiro KIMURA
Jun 22, 2018, 2:28:43 PM6/22/18
to
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.
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.
Chris H
Jun 22, 2018, 4:46:35 PM6/22/18
to
On Sat, 23 Jun 2018 02:56:35 +0900 (JST) "Yasuhiro KIMURA" <ya...@utahime.org> said
> From: "Chris H" <bsd-...@BSDforge.com>
> Subject: Re: Console is broken after updating to 11.2-RELEASE
> Date: Fri, 22 Jun 2018 06:13:39 -0700
>
> > Try adding the following to your loader.conf(5) file
> > (/boot/loader.conf):
> >
> > # Load SysCons driver
> > kern.vty=sc
> > # noisy boot
> > boot_verbose="YES"
> >
> > Hope this helps!
>
> Thank you for information. I added above lines to /boot/loader.conf
> and rebooted system. Then all boot messages are displayed and console
> works fine!
WooHoo! :-)
I could make further observations based on *why* that worked. But several
are likely, and I don't have enough info on your hardware. But now that
you are no longer "blind". You should have little trouble sorting out the
cause.
--Chris
> From: "Chris H" <bsd-...@BSDforge.com>
> Subject: Re: Console is broken after updating to 11.2-RELEASE
> Date: Fri, 22 Jun 2018 06:13:39 -0700
>
> > Try adding the following to your loader.conf(5) file
> > (/boot/loader.conf):
> >
> > # Load SysCons driver
> > kern.vty=sc
> > # noisy boot
> > boot_verbose="YES"
> >
> > Hope this helps!
>
> Thank you for information. I added above lines to /boot/loader.conf
> and rebooted system. Then all boot messages are displayed and console
> works fine!
I could make further observations based on *why* that worked. But several
are likely, and I don't have enough info on your hardware. But now that
you are no longer "blind". You should have little trouble sorting out the
cause.
--Chris
Rick Macklem
Jun 22, 2018, 4:57:20 PM6/22/18
to
Chris H wrote:
[stuff snipped]
switch virtual consoles, the screen would go blank until I power cycled the SVGA
monitor.
I switched to "sc" and the problem went away.
(This is an old Pentium 4 with what dmesg calls a "Generic VGA display".)
I don't see the same problem with a laptop of the same era.
Just in case it gives you a hint w.r.t. the problem, rick
[stuff snipped]
>>
>> Thank you for information. I added above lines to /boot/loader.conf
>> and rebooted system. Then all boot messages are displayed and console
>> works fine!
>
>WooHoo! :-)
>
>I could make further observations based on *why* that worked. But several
>are likely, and I don't have enough info on your hardware. But now that
>you are no longer "blind". You should have little trouble sorting out the
>cause.
I have no idea if this helps, but running a fairly recent head kernel, when I would
>> Thank you for information. I added above lines to /boot/loader.conf
>> and rebooted system. Then all boot messages are displayed and console
>> works fine!
>
>WooHoo! :-)
>
>I could make further observations based on *why* that worked. But several
>are likely, and I don't have enough info on your hardware. But now that
>you are no longer "blind". You should have little trouble sorting out the
>cause.
switch virtual consoles, the screen would go blank until I power cycled the SVGA
monitor.
I switched to "sc" and the problem went away.
(This is an old Pentium 4 with what dmesg calls a "Generic VGA display".)
I don't see the same problem with a laptop of the same era.
Just in case it gives you a hint w.r.t. the problem, rick
0 new messages