-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
=
FreeBSD-SA-18:07.lazyfpuSecurity Advisory
The FreeBSD Project
Topic:
On Wed, Jun 20, 2018 at 11:14 PM, Denis Polygalov wrote:
> What I did is following:
>
> # uname -a
> FreeBSD my_host_name 11.1-RELEASE-p10 FreeBSD 11.1-RELEASE-p10 #0: Tue
> May 8 05:21:56 UTC 2018
> r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
>
> # freebsd-update
Seems like I did not cc my reply to the mailing list.
Doing it now because I found a hint which may
lead to the cause of the reboot loop.
Removing:
linux_load="YES"
linprocfs_load="YES"
linsysfs_load="YES"
prevent the reboot loop in multi-user mode but
leave me without Linux emulation...
If you put those modules into rc.conf's kld_list, will it reboot as well?
According to the manpage, rc.conf is the faster way to load modules not
essential to booting.
On Thu, 21 Jun 2018, 3:15 pm Denis Polygalov, wrote:
> Seems like I did not cc my reply to the mailing list.
> Doing it now
Hi Gordon,
I was about to make the verbose dmesg output as requested but before doing so
I did just # kldload linux.so on the patched kernel. Nothing bad happend.
Then I restarted with linux_* lines enabled in the loader.conf and
choose verbose dmesg in boot menu. Boot and ... everything was OK.
Hmm. I'm unable to reproduce the error in any of my testing scenarios.
I apologize for not being to help further. As kib advised, if you can
please post a verbose dmesg from a successful boot along with where
you believe the panic occurs on a bad boot.
Gordon
On Thu, Jun 21, 2018 at 5:13 AM,
What I did is following:
# uname -a
FreeBSD my_host_name 11.1-RELEASE-p10 FreeBSD 11.1-RELEASE-p10 #0: Tue
May 8 05:21:56 UTC 2018
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
# freebsd-update fetch
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching
