AMD 7900 XTX crash on boot

I noticed this started roughly on the 20240220 image but I've been tracking down a crash when booting bazzite. I'm not sure if this is operator error and I missed a notice (I have the signing keys loaded so I think i'm basically good to go up to that point.) I'm attaching my kernel log that is showing several modules not loading and I believe these are contributing to the desktop not loading on every boot. Sometimes I get lucky and get a desktop, but today it seems to have come to a head with this build and I have had to roll back to the last pinned version I have on hand which was pre signed images.
chuck@RedDevil:/var/home/chuck$ rpm-ostree status
State: idle
Deployments:
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:latest
Digest: sha256:59c6ce6c2eb1ca2a6eb1d75dee9670c7abe9f3924d32a7f31f48e4a7910b2c1f
Version: 39.20240224.0 (2024-02-25T07:21:59Z)
Diff: 691 upgraded, 2 downgraded, 28 removed, 134 added
Initramfs: -I /etc/crypttab /etc/modprobe.d/amdgpu.conf

ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:latest
Digest: sha256:c8ddfbb10b2a51d96c2c6256e746afcfec9fd7c85e85007182b209704386c958
Version: 39.20240220.0 (2024-02-20T17:00:22Z)
Initramfs: -I /etc/crypttab /etc/modprobe.d/amdgpu.conf

● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:latest
Digest: sha256:828636b9d1ba23015c817bafe5acb7835a49530875bb0f34e66c3b31d7869612
Version: 39.20240112.0 (2024-01-12T16:51:48Z)
Initramfs: -I /etc/crypttab /etc/modprobe.d/amdgpu.conf
Pinned: yes
chuck@RedDevil:/var/home/chuck$ rpm-ostree status
State: idle
Deployments:
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:latest
Digest: sha256:59c6ce6c2eb1ca2a6eb1d75dee9670c7abe9f3924d32a7f31f48e4a7910b2c1f
Version: 39.20240224.0 (2024-02-25T07:21:59Z)
Diff: 691 upgraded, 2 downgraded, 28 removed, 134 added
Initramfs: -I /etc/crypttab /etc/modprobe.d/amdgpu.conf

ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:latest
Digest: sha256:c8ddfbb10b2a51d96c2c6256e746afcfec9fd7c85e85007182b209704386c958
Version: 39.20240220.0 (2024-02-20T17:00:22Z)
Initramfs: -I /etc/crypttab /etc/modprobe.d/amdgpu.conf

● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:latest
Digest: sha256:828636b9d1ba23015c817bafe5acb7835a49530875bb0f34e66c3b31d7869612
Version: 39.20240112.0 (2024-01-12T16:51:48Z)
Initramfs: -I /etc/crypttab /etc/modprobe.d/amdgpu.conf
Pinned: yes
Kernel log from trying to boot the 20240224 image: https://gist.github.com/lazypower/abb139513da537584304e4dc4e5bff0c Does anything stand out here that I'm not immediately seeing? Thanks!
Gist
gist:abb139513da537584304e4dc4e5bff0c
GitHub Gist: instantly share code, notes, and snippets.
Solution:
After booting the pinned image, I restarted the system and tried to load the 20240224 image and lo-and-behold its working. Really odd heisenbug that I'm fairly certain is something specific to my setup. I have a feeling its related to a "You might be running a broken bios" message I've seen in a couple of the logs. I'll post the follow up kernel boot in the gist link above but mark this message as resolution pending any further ideas to check into aside from a bios update. Thanks in advance for looking....
Jump to solution
1 Reply
Solution
lazyPower
lazyPower9mo ago
After booting the pinned image, I restarted the system and tried to load the 20240224 image and lo-and-behold its working. Really odd heisenbug that I'm fairly certain is something specific to my setup. I have a feeling its related to a "You might be running a broken bios" message I've seen in a couple of the logs. I'll post the follow up kernel boot in the gist link above but mark this message as resolution pending any further ideas to check into aside from a bios update. Thanks in advance for looking.
Want results from more Discord servers?
Add your server