Recent security patch cause reboot loop on 11.1 RELEASE
Gordon Tetlow
gordon at tetlows.org
Thu Jun 21 07:19:03 UTC 2018
On Wed, Jun 20, 2018 at 11:14 PM, Denis Polygalov <dpolyg at gmail.com> 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
> root at amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
>
> # freebsd-update fetch
> Looking up update.FreeBSD.org mirrors... 3 mirrors found.
> Fetching metadata signature for 11.1-RELEASE from update6.freebsd.org... done.
> Fetching metadata index... done.
> Inspecting system... done.
> Preparing to download files... done.
>
> The following files will be updated as part of updating to 11.1-RELEASE-p11:
> /boot/kernel/kernel
>
> Installing this update cause endless reboot loop.
>
> # cat /boot/loader.conf
> kern.maxfiles="32768"
> zfs_load="YES"
> linux_load="YES"
> linprocfs_load="YES"
> linsysfs_load="YES"
>
> # dmesg |grep CPU
> CPU: Intel(R) Xeon(TM) CPU 3.40GHz (3400.19-MHz K8-class CPU)
> FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
> SMP: AP CPU #1 Launched!
> SMP: AP CPU #3 Launched!
> SMP: AP CPU #2 Launched!
> cpu0: <ACPI CPU> on acpi0
> cpu1: <ACPI CPU> on acpi0
> cpu2: <ACPI CPU> on acpi0
> cpu3: <ACPI CPU> on acpi0
> acpi_perf0: <ACPI CPU Frequency Control> on cpu0
> est: CPU supports Enhanced Speedstep, but is not recognized.
> est: CPU supports Enhanced Speedstep, but is not recognized.
> est: CPU supports Enhanced Speedstep, but is not recognized.
>
> The machine is HP ProLiant ML350
Sorry to hear you are having a problem.
Just to confirm, this is running on hardware and not on a Xen
hypervisor, correct?
Assuming it's running directly on the hardware, can you see if setting:
hw.lazy_fpu_switch=1
in /boot/loader.conf makes any difference?
Is there any panic message?
Thanks,
Gordon
More information about the freebsd-security
mailing list