someone who is good at the economy please help me budget this. my family is dying
# systemd-analyze
Startup finished in 3min 36.134s (firmware) + 7.077s (loader) + 7.043s (kernel) + 7.608s (userspace) = 3min 57.864s
zhenech@chaos.social
replied 02 Nov 2026 09:44 +0000
in reply to: https://benjojo.co.uk/u/benjojo/h/M1L39smB35n33525Bd
benjojo
replied 02 Nov 2026 09:45 +0000
in reply to: https://chaos.social/users/zhenech/statuses/117546198460368475
SpaceLifeForm@infose..
replied 02 Nov 2026 09:44 +0000
in reply to: https://benjojo.co.uk/u/benjojo/h/M1L39smB35n33525Bd
benjojo
replied 02 Nov 2026 09:47 +0000
in reply to: https://infosec.exchange/users/SpaceLifeForm/statuses/117546200075150878
@SpaceLifeForm I don't think so? This is a universal thing over all DDR5 machines I operate. This one is actually quite short in the grand scheme of things as it's "only" 6x64G, rather than a fully loaded 12
SpaceLifeForm@infose..
replied 02 Nov 2026 10:38 +0000
in reply to: https://benjojo.co.uk/u/benjojo/h/9djc6mBw41TNk857rc
The numbers do not make sense to me. But consider the source. Funny how it attributes about 7 secs to firmware, loader, and kernel. Each. I see no way that systemd could know in any way how much time the loader spent as systemd is a userland process that does not even exist until the kernel has started it.
benjojo
replied 02 Nov 2026 11:19 +0000
in reply to: https://infosec.exchange/users/SpaceLifeForm/statuses/117546413872192566
Imagine being capable of reading source code and understanding things! systemd is reading UEFI boot measurements. https://github.com/systemd/systemd/blob/main/docs/BOOT_LOADER_INTERFACE.md Loader takes 7 seconds because GRUB has a standard debian 5 second menu wait, and probe/fetch/decompress easily takes the other 2 seconds. I don't know where you are drawing a link to power supply being bad and boot times taking long (but the rest of the machine is fine? and has been fine for ~1Y+), a bizarre conclusion to make.
I see no way that systemd could know in any way how much time the loader spent as systemd is a userland process that does not even exist until the kernel has started it.
benjojo
replied 03 Nov 2026 10:18 +0000
in reply to: https://infosec.exchange/users/SpaceLifeForm/statuses/117551407405520853
benjojo
replied 03 Nov 2026 10:29 +0000
in reply to: https://infosec.exchange/users/SpaceLifeForm/statuses/117552003128713207
gorplop@pleroma.m68k..
replied 02 Nov 2026 15:38 +0000
in reply to: https://infosec.exchange/users/SpaceLifeForm/statuses/117546413872192566
hennichodernich@radi..
replied 02 Nov 2026 12:53 +0000
in reply to: https://benjojo.co.uk/u/benjojo/h/M1L39smB35n33525Bd
@benjojo does it at least show some screen output while computing the timing? My X99 board shows a black screen for about half a minute before the first d screen output.
benjojo
replied 02 Nov 2026 16:45 +0000
in reply to: https://radiosocial.de/users/hennichodernich/statuses/117546943740535749
@hennichodernich Gigabyte also leaves you in the dark (though the IPMI does say that it's in "Chipset initialization" state), the supermicro H13 board does give you this static image
hennichodernich@radi..
replied 02 Nov 2026 16:58 +0000
in reply to: https://benjojo.co.uk/u/benjojo/h/h4WTwzX121Xf2Z823k
@benjojo feels like ages to boot, but *this* seems a bit long to me. I suspect this "Machinist X99 PR9-H" board might have a buggy UEFI firmware providing wrong values.
benjojo
replied 02 Nov 2026 18:17 +0000
in reply to: https://radiosocial.de/users/hennichodernich/statuses/117547907180764056
benjojo
replied 02 Nov 2026 09:43 +0000
in reply to: https://benjojo.co.uk/u/benjojo/h/M1L39smB35n33525Bd
I get that modern DDR5 memory controllers need to solve at least 50 electrical engineering sudokus before they can actually use a DIMM, but when you have even a moderately loaded system it takes a whole era to reboot, I fear what DDR6 will look like
wolf480pl@mstdn.io
replied 02 Nov 2026 10:43 +0000
in reply to: https://benjojo.co.uk/u/benjojo/h/WK4jnfT69zWxrp8X1S
@benjojo
doesn't the BIOS have an option to remember the solutions from previous boot, then on a new boot quickly check if they still work, and only do the full memory training if they don't?
benjojo
replied 02 Nov 2026 11:20 +0000
in reply to: https://mstdn.io/users/wolf480pl/statuses/117546431899237510
@wolf480pl I think this is more common on desktop class boards r than workstation/server ones, regardless I suspect a good % of the time is also spent doing a cursory RAM test or something similar
mentalist@mastodon.s..
replied 02 Nov 2026 09:44 +0000
in reply to: https://benjojo.co.uk/u/benjojo/h/WK4jnfT69zWxrp8X1S
WiteWulf@cyberplace...
replied 02 Nov 2026 09:51 +0000
in reply to: https://benjojo.co.uk/u/benjojo/h/WK4jnfT69zWxrp8X1S
@benjojo about 20 years ago we got one of the old Sun “Thumper” storage chassis. They had 48 spinning SATA HDDs in them, the BIOS took an absolute age to POST!
theartlav@anarres.fa..
replied 02 Nov 2026 10:26 +0000
in reply to: https://benjojo.co.uk/u/benjojo/h/WK4jnfT69zWxrp8X1S
mxk@hachyderm.io
replied 02 Nov 2026 15:19 +0000
in reply to: https://benjojo.co.uk/u/benjojo/h/WK4jnfT69zWxrp8X1S
@benjojo way to boot modern systems quickly:
Boot with as little RAM as possible and then hotplug the rest of it later during startup.
lmb@fosstodon.org
replied 02 Nov 2026 10:36 +0000
in reply to: https://benjojo.co.uk/u/benjojo/h/M1L39smB35n33525Bd
radex@social.hackers..
replied 02 Nov 2026 10:49 +0000
in reply to: https://benjojo.co.uk/u/benjojo/h/M1L39smB35n33525Bd
@benjojo as someone who’s fairly new at dealing with bare metal servers… god I hate this stuff so much. Feels backwards that my 5yo laptop boots in 30s but a 96-thread beast takes a good 5 minutes. (And much more to gracefully reboot due to the time it takes for some services to cleanly exit)
madduci@mastodon.soc..
replied 02 Nov 2026 11:07 +0000
in reply to: https://benjojo.co.uk/u/benjojo/h/M1L39smB35n33525Bd
