Fedora doesn't boot with amdgpu -22 error

Ask Fedora
1

I’ve been using my system and suddenly it froze (might be because I’ve inserted a usb stick). After 2-3 minutes I did forced shut down and after that Fedora never booted again no matter what kernel version I use. If I change rghb quiet to nomodeset it works. I’ve been “debugging” the problem with LLM, but it’s just a crappy way and it didn’t solve anything.
dmesg | grep -Ei “amdgpu|gpu|drm|fw” showed “probe with driver amdgpu failed with error -22”.
I’ve tried restoring an older snapshot, upgrading my system, force restoring dracut, reinstalling all the mesa and linux-firmware packages and it just doesn’t work.
My specs are: Ryzen 5 3600, RX570, DDR4 2400Mhz 8x2, ASrock A320.
I would really appreciate any help, as a beginner I have no clue how to debug and fix it.

image
image1080×607 180 KB

2

I hope those inputs may lead into something:

dmesg | grep -i "failed to"
    0.424226] amd_pstate: Failed to initialize CPU 0: -22
[    0.426225] amd_pstate: Failed to initialize CPU 1: -22
[    0.428223] amd_pstate: Failed to initialize CPU 2: -22
[    0.430229] amd_pstate: Failed to initialize CPU 3: -22
[    0.432224] amd_pstate: Failed to initialize CPU 4: -22
[    0.434229] amd_pstate: Failed to initialize CPU 5: -22
[    0.436224] amd_pstate: Failed to initialize CPU 6: -22
[    0.438228] amd_pstate: Failed to initialize CPU 7: -22
[    0.440224] amd_pstate: Failed to initialize CPU 8: -22
[    0.442230] amd_pstate: Failed to initialize CPU 9: -22
[    0.444224] amd_pstate: Failed to initialize CPU 10: -22
[    0.446230] amd_pstate: Failed to initialize CPU 11: -22
[    0.446241] amd_pstate: failed to register with return -19
[    7.588119] asus_wmi: failed to register LPS0 sleep handler in asus-wmi

sudo dmesg | grep -i firmware 
[    0.000232] Spectre V2 : Enabling Speculation Barrier for firmware calls
[    0.191790] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[    0.237516] acpi PNP0A08:00: [Firmware Info]: ECAM [mem 0xf8000000-0xfbffffff] for domain 0000 [bus 00-3f] only partially covers this bridge
[    6.087693] SELinux:  Permission firmware_load in class system not defined in policy.
[    6.968131] systemd[1]: systemd-boot-clear-sysfail.service - Clear SysFail Entry If The Boot Is Successful was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/LoaderEntrySysFail-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
[    6.968491] systemd[1]: systemd-hibernate-clear.service - Clear Stale Hibernate Storage Info was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67).
3

OK - so you have a system which boots ok if you specify nomodeset on the kernel parameter, but fails if you just allow it to try to boot normally.

  1. Restart your machine, but within grub remove rhgb and quiet so that you get all the boot messages on screen. Let it sit there for 10 minutes (this is just to let things run to the point where if they were ever going to complete, they will probably have done so.)
  2. Press Ctrl+Alt+F5 - if you get a TTY, login in and issue the shutdown command.
  3. This time boot the machine by adding in your nomodeset parameter. Hopefully this fires you up to a graphical desktop, just to make things easier for you.
  4. Open a terminal, and issue the command journalctl --no-hostname --no-pager -b -1 | fpaste. the -b -1 part indicates we want to look at the log from the previous boot - the one you just made demonstrating the issue.
  5. Post the URL it gives you here - ideally you’d upload the entire journal here, but it will be too large so sticking it into a pastebin is the next best option and I can cut and paste the relevant bits in here for posterity when we work out what the issue is.
  6. Post the output from inxi -Fzxx here too. Shows us your hardware, verisions, which driver is loaded and so on.