Slow boot times.

Within the past week i've been experiencing slow bootup times.
kade@fedora:~$ systemd-analyze
Startup finished in 24.880s (firmware) + 19.534s (loader) + 5.949s (kernel) + 1min 2.170s (initrd) + 11.367s (userspace) = 2min 3.902s
graphical.target reached after 11.358s in userspace.
kade@fedora:~$ systemd-analyze
Startup finished in 24.880s (firmware) + 19.534s (loader) + 5.949s (kernel) + 1min 2.170s (initrd) + 11.367s (userspace) = 2min 3.902s
graphical.target reached after 11.358s in userspace.
ive attached a systemd-analyze blame thing within the text document along with https://paste.centos.org/view/24a317c9 to show device info. Dunno what could've done it. its not a big issue as I only boot my pc up like once a day but its a new occurance.
69 Replies
Niklas ⚡
Niklas ⚡2mo ago
Reading the systemd-blame log, I get the impression that NetworkManager is having problems establishing a connection or initializing.
kade
kade2mo ago
Shutdowns also take a hot minute as well.
Niklas ⚡
Niklas ⚡2mo ago
@kade can you get me a full dmesg / journalctl log and a systemd-analyze critical-chain?
kade
kade2mo ago
If I knew how to get a dmesg yes :happy_green_trees:
Niklas ⚡
Niklas ⚡2mo ago
sudo dmesg
Niklas ⚡
Niklas ⚡2mo ago
Yeah I don't see anything particularly wrong here I'm out of ideas
kade
kade2mo ago
I never had any ideas to begin with. I appreciate the help though maybe someone else has ideas
wolfyreload
wolfyreload2mo ago
I see that you are using the testing branch of bazzite in the last week or so if I look at your pastebin. Is the boot faster if you boot the stable branch instead?
kade
kade2mo ago
no @nickname suggested I try the testing branch to see if it fixed the issue and it didnt I just switched to testing like 3 hours ago
wolfyreload
wolfyreload2mo ago
ohhhh ok, never mind then 🙂
Leigars
Leigars2mo ago
I have the same issue, very slow to boot and sometimes it boots into a black screen and I have to hard reset my PC
kade
kade2mo ago
What hardware are you running
Leigars
Leigars2mo ago
hard drive is nvme SSD
No description
kade
kade2mo ago
And how recent did this start to happen
Leigars
Leigars2mo ago
ever since I installed Bazzite yesterday for the first time
kade
kade2mo ago
That’s odd Because mine was a month after I started using it
Leigars
Leigars2mo ago
it's weird because when I restart for example it takes like a minute or two to shutdown and then it boots into a black screen instead of the login screen I have to hard reset the pc to load it properly
kade
kade2mo ago
are you using wayland or x11
Leigars
Leigars2mo ago
wayland
kade
kade2mo ago
that might be your issue with the black screen but again I have no idea and just trying to get more information for the people who help here cuz i still have the same issue
Leigars
Leigars2mo ago
any update on this issue? have you been able to fix it? I'm using X11 now instead of wayland but the issue persists
tad
tad2mo ago
Same. Using a docked laptop so it's especially annoying.
DudeGuyKhaine
DudeGuyKhaine2mo ago
Same problem here. Running on desktop pc. I have to do a hard reset every time and then it boots normally.
Leigars
Leigars2mo ago
I made these changes to the system settings, booting times seems normal now, however shutting down takes like 5 minutes
No description
tryhardsoccermomswag
are you all on KDE Plasma? im starting to think plasma 6 wayland (possibly X11) and nvidia drivers are having issues
JohnyLPM
JohnyLPM2mo ago
for me it seems to occur due to the systemd-journal-flush service taking its sweet time, sometimes also ostree-finalize taking ups of 5 mins even after all the time taken during the rebase prior to the shutdown/reboot for the journal-flush service I read about attempting to change the Storage=persistent in the config file, but I've no idea how or if it would help at all
aednichols
aednichols2mo ago
https://discord.com/channels/1072614816579063828/1229478191786098791/1231678147922100265 Seeing something very similar with ~25s firmware times. I can make it go away with a fresh install, but today I rebooted from Fedora 39 to 40 and it was back And I'm on Gnome I thought I had fixed it but it came back
tryhardsoccermomswag
oh so it's happening on GNOME now
aednichols
aednichols2mo ago
At least something very similar, yeah
JohnyLPM
JohnyLPM2mo ago
UPDATE: I've since performed a manual update using Bazzite's System Update (had tried yesterday but it didn't seem to apply for some reason on reboot) and now upon testing a few reboots as well as manual shutdown and poweron, both on X11 and Wayland, neither the SDDM issue nor the boot/shutdown times seem to be occuring, will report again if they do (also, my update seems to have had something related to kernel modules and, consequentially, kmod reinstalling nvidia)
Leigars
Leigars2mo ago
I manually updated the system, but I still have the long shutdowns. Changing to Plasma X11 seems to have fixed the booting issues though
JohnyLPM
JohnyLPM2mo ago
yeah, it returned for me too, so idk I'll try that too, but I really need Wayland on the day-to-day, so I'll see if getting in the rhythm of logging out, logging back in with X11 and only then shutting down/rebooting every time helps
mervius
mervius2mo ago
So I can boot up after updating from 39 to 40 But any subsequent boots on 40 are just a black screen with no login screen sometimes the loading screen before the black scree takes a while as well
Leigars
Leigars2mo ago
are you using wayland?
mervius
mervius2mo ago
I believe so haven't changed anything Not sure why it would work for the first boot after updating then not any boots after that
Leigars
Leigars2mo ago
try to change to X11, it fixed the boot black screen for me
mervius
mervius2mo ago
Rolling back to 39 works then running ujust update
JohnyLPM
JohnyLPM2mo ago
yeah, this didn't help, I was using X11 and was rebooting to check if watchdog disabling would budge (it hadn't before, and spoilers, it still didn't) and once again, even with SDDM already set at X11, the long shutdown time and black screen on boot still occurred (had to do the dance of shutting down again and turning back on)
mervius
mervius2mo ago
hmm so it is booting and you see a cursor, right? just nothing else? no login screen
JohnyLPM
JohnyLPM2mo ago
yeah just blackness and the good 'ol adwaita cursor and then upon reboot it's back to normal but this is known already, although the cause I think still isn't
mervius
mervius2mo ago
rebooting doesn't seem to work for me or, well, not consistently rolling back and re-updating always does, though
JohnyLPM
JohnyLPM2mo ago
hmm, not sure, but every time it happened I just give the power button a tap, it knows to shutdown and then I turn it back on and it's good
mervius
mervius2mo ago
because 39 always boots
JohnyLPM
JohnyLPM2mo ago
right after the issue with the journal still persists, hence this topic is there a way we can just rebase to a previous version I wonder? by now I'm pretty sure I can't rollback to before the update
mervius
mervius2mo ago
i mean you could download one of the older images then turn off the update timer not sure where those are hosted, though
JohnyLPM
JohnyLPM2mo ago
yeah, that's the thing, do we have where to pull them from? I might still have the old one in my drive, but not sure if I'm lucky I suppose that'd be a solution, but otherwise it doesn't seem optimal
mervius
mervius2mo ago
I literlly just overwrote my 39 installation media could try a fresh install of 40 but idk if that'd fix it
JohnyLPM
JohnyLPM2mo ago
yeah, that's what I was thinking
mervius
mervius2mo ago
but if I do a fresh 40, I lose my pinned 39
JohnyLPM
JohnyLPM2mo ago
pull request seem to indicate a fix for another issue is in the works of being put in the iso, maybe if updating after that doesn't change anything I might give it a shot
mervius
mervius2mo ago
unless I can figure a way to keep it
JohnyLPM
JohnyLPM2mo ago
I mean, I don't know how laissez faire they are about this, but potentially someone here might be able to provide the old iso or otherwise, if it weren't a problem, I might be able to share mine if I have it
mervius
mervius2mo ago
hmm
JohnyLPM
JohnyLPM2mo ago
the again though, that wouldn't help, would it? isn't the image pulled at install time and it would just pull the current one?
mervius
mervius2mo ago
actually I should have a 39 iso on my laptop
JohnyLPM
JohnyLPM2mo ago
I'll check in a bit but if I have it, I should have both gnome and kde nvidia for bazzite 39 and then ofc the kde nvidia for bazzite 40 that was hosted shortly after official release
mervius
mervius2mo ago
god it takes so long to shut down :u
JohnyLPM
JohnyLPM2mo ago
yeah, same we probably shouldn't be populating this channel so much might make it harder to check on later for review
mervius
mervius2mo ago
yeah I have the iso from april 22
JohnyLPM
JohnyLPM2mo ago
nicee yepp, still have them, my 39 iso is from april 17
kade
kade2mo ago
kade@fedora:~$ systemd-analyze
Startup finished in 8.502s (firmware) + 2.628s (loader) + 5.215s (kernel) + 3.545s (initrd) + 11.935s (userspace) = 31.826s
graphical.target reached after 11.925s in userspace.
kade@fedora:~$ systemd-analyze
Startup finished in 8.502s (firmware) + 2.628s (loader) + 5.215s (kernel) + 3.545s (initrd) + 11.935s (userspace) = 31.826s
graphical.target reached after 11.925s in userspace.
somehow it fixed itself
JohnyLPM
JohnyLPM2mo ago
it did? I have a similar output and still experience slow shutdown times due to journal-flush/ostree-finalize (if a rebuild occurs)
Startup finished in 4.159s (firmware) + 6.126s (loader) + 1.551s (kernel) + 7.712s (initrd) + 13.106s (userspace) = 32.655s
graphical.target reached after 13.091s in userspace.
Startup finished in 4.159s (firmware) + 6.126s (loader) + 1.551s (kernel) + 7.712s (initrd) + 13.106s (userspace) = 32.655s
graphical.target reached after 13.091s in userspace.
kade
kade2mo ago
for me the original issue was slow boot times and now its fixed
JohnyLPM
JohnyLPM2mo ago
ohh, true mb
kade
kade2mo ago
I did switch networks so maybe thats something to note because someone looked at my logs said networkmanager was being slow
JohnyLPM
JohnyLPM2mo ago
in that case maybe this topic should be closed and a new one opened?
kade
kade2mo ago
still need to check shutdown times as that was an issue but doesnt bother me also doesnt seem to hurt to keep it open since slow boot times could be anything
JohnyLPM
JohnyLPM2mo ago
fair enough, I should probably open another one for the separate SDDM issue though