Created attachment 201205 [details]
dmesg and pciconf -lv outputs (11.2-RELEASE)
Hardware: HP ProLiant ML350-G4 (yes, it is quite old).
Boot from: FreeBSD-12.0-RELEASE-amd64-disc1.iso
Verbose boot: enabled
ACPI: enabled or disabled - doesn't matter, the result is the same.
On the screen:
/boot/kernel/kernel text=0x1678a ... (SKIPPED)
Loading configured modules...
can't find '/boot/entropy'
<-- nothing printed after the line above -->
The CD disk and USB CD drive are OK, both tested on other machines.
This machine have no problems booting and running 11.2-RELEASE.
This behavior was dicovered during attempt of updating from
11.2-RELEASE to 12.0-RELEASE (using freebsd-update).
Interestingly, during hang after freebsd-update the
line (can't find '/boot/entropy') was _not_ printed.
Output of dmesg and pciconf (when booted in 11.2-RELEASE) are attached.
Created attachment 201459 [details]
dmesg on SuperMicro X6DH8-G2+
Created attachment 201460 [details]
pciconf on SuperMicro X6DH8-G2+
Same thing here with an SuperMicro X6DH8-G2+. Dmesg and pciconf -lv also attached, created using FreeBSD 11.2.
Same issue here on a Dell SC1425:
CPU: Intel(R) Xeon(TM) CPU 3.20GHz (3200.17-MHz K8-class CPU) Origin="GenuineIntel" Id=0xf4a Family=0xf Model=0x4 Stepping=10
12.0-RELEASE i386 will boot, amd64 will not. PXE or local harddisk makes no difference. Booting on serial console. I am using the release bootonly images from ftp.freebsd.org.
This seems to be the same issue as is being reported here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234676 and on the forum at https://forums.freebsd.org/threads/freebsd-12-cant-find-boot-entropy.68265/
Tried both efi.rt.disabled=1 and hint.apic.0.disabled="1" as these were mentioned, but no difference.
BTW: 11.2 panics on boot with hint.apic.0.disabled="1":
panic: No usable event timer found!
cpuid = 0
KDB: stack backtrace:
#0 0xffffffff80b3d567 at kdb_backtrace+0x67
#1 0xffffffff80af6b07 at vpanic+0x177
#2 0xffffffff80af6983 at panic+0x43
#3 0xffffffff810af4bd at cpu_initclocks_bsp+0x3dd
#4 0xffffffff810ddf65 at cpu_initclocks+0x15
#5 0xffffffff80a96130 at initclocks+0x20
#6 0xffffffff80a92898 at mi_startup+0x118
#7 0xffffffff8031002c at btext+0x2c
But anyway, that is not related to this bug. Verbose boot shows nothing more than the "entropy not found" error, after which console stays empty.