Date: Sun, 14 Feb 2021 19:16:29 -0500 From: Mark Johnston <markj@freebsd.org> To: Leon Dietrich <doralitze@chaotikum.org> Cc: freebsd-stable@freebsd.org Subject: Re: Microcode update prevents boot Message-ID: <YCm9XZLnJ6Uzrpc0@spy> In-Reply-To: <a7a76dc2-dcf6-7d3a-00ac-a8474126a30d@chaotikum.org>
index | next in thread | previous in thread | raw e-mail
On Sun, Feb 14, 2021 at 02:01:14PM +0100, Leon Dietrich wrote: > Hi there, > > I already worked around the issue myself. I'm just writing this here in > case someone else may have the same issue and is seeking an answer. > > > I recently upgraded the intel cpu microcode update package. Since then > the boot process hang at the stage where the other cpu cores where > enabled (shortly after enabling acpi). In order to resolve the issue one > has to boot in safe mode (not single user mode!) and comment (or remove) > the lines enabling the cpu microcode update on boot in > /boot/loader.conf. One can and should reboot then. > > After making these changes the system boots again and all cores are > started and SMT works as well. One should note that one's not running > the newer microcode (including some security-) fixes. Having > microcode_update_enable="YES" in /etc/rc.conf doesn't prevent booting > and does not cause noticeable instability. > > For reference: Im running FreeBSD 12.1 on a supermicro embedded board > with intel xeon E3-1585L v5 cpus. > > > I hope someone will find this info useful. I see that r347931 was not merged to stable/12 branch, but the lockless delayed invalidation changes were indeed present in 12.1. Could you see if the hang persists when boot-time ucode loading is enabled and vm.pmap.di_locked=1 is configured? Note that you could apply both configurations at the loader prompt, i.e., without having to edit loader.conf and boot in safe mode to revert the change.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YCm9XZLnJ6Uzrpc0>