After recent updates, I’ve started getting significant errors regarding my AMD GPU. For context, I’m on a Lenovo laptop with an AMD Ryzen 7 7735U with Radeon graphics. Things seemed to be functional for a while, and still appear to be mostly operational, however now certain things give me significant lagging and bugs (brightness controls seem to be an issue with it as well).
Relevant dmesg errors start with:
“amdgpu 0000:04:00.0: [drm] ERROR Error getting DMUB FW meta info: 4
amdgpu 0000:04:00.0: failed to load ucode DMCUB(0x3F)
amdgpu 0000:04:00.0: psp gfx command LOAD_IP_FW(0x6) failed and response status is (0xFFFF0008)
amdgpu 0000:04:00.0: [drm] Wait for DMUB auto-load failed: 3”
Which is then following by a long series of repeated:
“amdgpu 0000:04:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data”
In addition, mcelog.service is failing with the following error:
“mcelog: ERROR: AMD Processor family 25: mcelog does not support this processor. Please use the edac_mce_amd module instead.
CPU is unsupported”
This appears to be related to a recent Arch Linux problem as well:
It is recommended in this discussion to downgrade the AMD firmware (or potentially ddcutil), however I’m unsure how to downgrade these packages properly on Fedora.
Is anybody else having this issue? Is anyone aware of work being done to resolve this? What would be the best way for me to report this?
Update on a quick fix for this:
I downgraded the package amd-gpu-firmware and it appears to have resolved the issue for the time being, however I’m not sure if there are any issues or potential vulnerabilities that were patched with recent updates.
Hopefully this will be resolved upstream by Fedora soon and I can get back up-to-date.
Thank you all for the assistance.
I can confirm the same issue on Fedora 44 KDE with a Ryzen 5 7535U / Radeon 680M.
With kernel 7.2.5, my external HDMI display was detected by the system, but received no signal. The kernel log was filled with DMUB/DMCUB errors, including Error queueing DMUB command: status=2 and EDID CEA parser failed.
Booting back into kernel 7.2.4 fixed the HDMI output immediately. So for now I’m using 7.2.4 as a workaround.
Your logs correlate largely to a bug in the linux-firmware (more precisely, that of amd gpu), which is supported by the fact that your Ryzen contains the affected AMD graphics: 680M.
As already suggested at one of the other topics about this case, this should be avoided because it reverts several updates, including security critical updates (it ends up in the state of March). One alternative to avoid this is the command I suggested in the workaround. Another way is to enable updates-archives for the command (in one of the topics I think its already contained).
Thank you very much for your assistance with this.
I was a bit concerned with how far back dnf downgrade took amd-gpu-firmware, but wasn’t sure of the best way to get it to downgrade to a more recent version.
Your command seems to have resolved the issue on my computer for the time being, I’ll keep an eye on the updates to see when it is fixed upstream.
I appreciate your help with this and the information you provided.
Final solution for those with the 680M problem (issues about the solution, please in the topic I posted it and add the data I requested for that case!):
Because there had been already several, partially dangerous, ideas of how to mitigate in some of the topics about this, I select this as solution so that users are led here before they attempt one of them: the OP is free to change this choice if they disagree!
Thank you very much for all your assistance here. The latest update is working for me with no problems. I appreciate your responsiveness and the speed with which this was patched.
The thanks for that go to our firmware maintainer and the maintainers of the upstream AMD code, and of course all users who reported their issue and provided data