On 1/5/23 02:22, Sylvain Saboua wrote:
https://youtu.be/lzGT1TAGG1YOpenBSD 7.2 (GENERIC.MP) #758: Tue Sep 27 11:57:54 MDT 2022 [email protected]:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8449818624 (8058MB) avail mem = 8176320512 (7797MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xda571018 (40 entries) bios0: vendor American Megatrends Inc. version "4.6.5" date 11/11/2013
Not exactly a new machine (i.e., my vintage. :) ) ...
cpu0: Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz, 2693.94 MHz, 06-2a-07
...ten year old processor. ...
ahci0 at pci0 dev 31 function 2 "Intel 7 Series AHCI" rev 0x04: msi, AHCI 1.3 ahci0: port 0: 6.0Gb/s
...
sd0 at scsibus1 targ 0 lun 0: <ATA, Samsung SSD 870, SVQ0> naa.5002538f40c128a7 sd0: 953869MB, 512 bytes/sector, 1953525168 sectors, thin
good. don't think that was factory. :) ...[snip]... That didn't seem *that* slow to me. For giggles, I compared your startup time vs. my netbook with full disk encryption. It turns out, you are right, you actually were slower for the kernel load (once the kernel loaded, your system kicked my netbook's butt) What you are seeing is the initial kernel load taking place. The OS is not running then -- the firmware has loaded /boot and it is pulling up the kernel a little bit at a time through the system firmware and with only one core jumping between the system firmware, the boot code, decrypting data, etc., and it has 22MB to load (that used to be SO HUGE!). You are 100% dependent upon the system firmware at this point, OpenBSD is not running yet (OpenBSD provided code, yes, the kernel, no). I don't think this counts as an OpenBSD bug at all, it's just the way your machine works until a modern OS is loaded and takes over managing the hardware. /boot has only a few ways to get data off the disk, it basically ends up working through somewhat updated (for large disk) tools that existed on the 1982 IBM XT. Looks like you are using UEFI boot -- you might want to try it with BIOS/Legacy. That's an old enough machine that UEFI might not have been the optimal way to boot that machine. You could see if there's a newer BIOS for your computer. Nick.
