Kernel Panic after update
Hello guys, yesterday I did an update on Bazzite 41 (see details below). It's not the first time I update, I think it mostly update the nvidia drivers.
Booting up right after the I got a black screen (after bootloading ostree-0). Try rebooting and now sometimes I have a black screen and sometimes a kernel panic (see attached pic).
Ostree-1 is working just fine, so that's ok I did not lost anything, but it's the first time I use a atomic OS and I do not quite know what to do to fix ostree-0. Would you guys be kind enough to help a newby like me ?
Details on OS/Hardware:
Operating System: Bazzite 41
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.1
Kernel Version: 6.12.10-202.bazzite.fc41.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz
Memory: 15.5 Gio of RAM
Graphics Processor: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7B49
System Version: 1.0
Solution:Jump to solution
boot into ostree 1 (the working one). Open the terminal and then run
rpm-ostree rollback this will swap the working and the broken update around so ostree 0 will be the working one. You might want to disable automatic updates for a little with ujust toggle-updates55 Replies
Solution
boot into ostree 1 (the working one). Open the terminal and then run
rpm-ostree rollback this will swap the working and the broken update around so ostree 0 will be the working one. You might want to disable automatic updates for a little with ujust toggle-updatesSame just happened to me when I updated.
We're in this together! I have the exact same issue, and I'm also on Nvidia KDE although I'm on an Acer Predator PH315-54 laptop. I'm the person who posted the issue on Lemmy, and someone else on Discourse linked to it (in the comments here: https://universal-blue.discourse.group/t/bluefin-41-kernel-panic-during-boot/5101/10 also on Bazzite) because they're having the same problem. I've already rolled back, that's the obvious first step for anyone else in the situation, and someone should probably open an issue on GitHub.
Universal Blue
Bluefin 41 - Kernel Panic during boot
My findings: Version: 41.20250119.1 (2025-01-19T06:04:01Z) - Not working Version: latest-41.20250119 (2025-01-19T05:04:41Z) - Working This is really odd because they seem to be the same/similar versions GTS also works so I don’t think it’s a regression
what image are you guys on
The Nvidia GTX 9xx-10xx image.
Just updated to bazzite-nvidia:stable.41-20250131 and kernel panic
So which images are affected
The legacy ones broke right?
It's not a kernel panic
The initramfs is corrupted
Init crashes
yes the bazzite-nvidia:stable for GTX 9xx-10xx
@antheas bazzite:stable-41.20250131 seems to be fine, probably just nvidia image then. Going to test gnome
Thanks
I think something in the Nvidia legacy images broke dracut
bazzite-nvidia-open:41.20250131 boots fine
Find the initramfs in the broken image and compare its size to the working one
Also try the testing build from yesterday
It's very likely it's a one-off freak accident
So if we rebuild it will work
@antheas bazzite-nvidia:testing-41.20250131 working fine. Can't we just add a tag stable-41.20250131.1 and move the stable tag to testing-41.20250131 for bazzite-nvidia or will that mess up something?
Going to check gnome now
No, @HikariKnight can we rebuild stable?
But he should be able to, we need to figure out a way to do that
I'm currently out on errands with my mom. I will try navigate GitHub on my phone and try rebuild asap
My mom was talking to a clerk so I managed to have time to start a rebuild @antheas
Thanks hopefully no oupsies in stable
Ping me if you need another build. I will try to start when I have a moment free.
Going to be a long day for me 😅
Unfortunate hang in there
@antheas tested bazzite-gnome-nvidia:stable-41.20250131 and it's booting fine so it looks like it was just a once off issue with the bazzite-nvidia image.
9/22 of the build jobs failed
Which oned
Looks like the one that we want failed
@antheas every nvidia image build failed.
Is this being caused by negativo bumping to version 570.86.16 from .15 yesterday?
Do you have an old version of the iso to download? If I install a stable version without nvidia, it will be a pain to configure
You should be able to install bazzite-stable.iso and then just rebase to the not broken nvidia stable image with this terminal command
bazzite-rollback-helper rebase bazzite-nvidia:stable-41.20250127 @Jnzthe build fail yes
@j0rge can you drop an akmods build?
what do you mean, just build akmods?
ye
negativo drift
we need to rebuild bazzite-nvidia stat
thanks
Have the same issue on my Lenovo Legion Y520 (GTX1050), updated to 20250131 and got kernel panic for libsystemd-core. Welp, time to pin my 0127 and wait I guess
@HikariKnight hit the build button
Done
@antheas / @HikariKnight bazzite-nvidia build failed with same error again.
Is the cause of the kernel panic related to the skew or is it a separate issue specific to certain hardware configs?
Image is broken, probably data corruption when building it
ok guys, we rolled back bazzite-nvidia
I'll let my buddy know, thanks!
So if we’re currently having this issue should we just boot into the working images and rollback?
Update
Oh it’s fixed with the update? Got it
Out of curiosity, if I boot into the working images and update, does that push the “broken” image to slot 1 or remove it.
best surefire way to guarantee the broken image is removed is to boot the working image and issue a
rpm-ostree rollback
which makes both 0 and 1 into the old imageThat’s what I was going to do, wanted to make sure it made sense. Thanks for confirmation 🙂
then just update from there
i havent had to do an update from
1 myself yet so i am just saying what i know for sure wont leave you with 2 broken images in worst case 🙂Better to be safe hah
there is also
sudo ostree admin pin 1 to pin the old image to guarantee you always have a working image in 2 once it gets bumped off its spot as ostree:1
then you can just unpin it later with sudo ostree admin pin --unpin 2 and it will just clean itself up iircupdating from 1 replaces 0 slot
pinning is always a good idea
I did the rpm-ostree rollback and this is my rpm-ostree status
So as far as I understand 0 is now the older working image which I'm using now
1 is the broken image
Is it safe for me now to do an update from image 0?
I'd run
sudo ostree admin pin 0 that will pin your current image so if the update goes badly then you always have access to your image from 20250127 until you unpin it
sudo ostree admin pin --unpin x where you replace x (starts at 0) to unpin an imageThank y'all for being so helpful. Just ran into this problem and did some kernel panicking myself 🙃
question about pinning though-- my log looked exactly like bobby's. I read through this and pinned both 20250127 and 20250131 (ostree 0 / ostree 1 respectively), is the way forward just running a manual update from
1 ?
also will the pinned images appear as 2 and 3?this
they will be lowered to 2 and then 3 (if you pinned 2 images in total) as neccessary then remain there
Perfect. Thank you! Running a
ujust update rn. Looks like that should do it.Just as a question
Will you still provide new images for bazzite-nvidia or is it ded?
yes
we are having nvidia driver issues so no new stable yet
not with the drivers themselves
version mixup
Thank you for the quick reply and clarification:bobofrfr:
bazzite-nvidia is supported for as long as nvidia releases new versions of the proprietary kernel module