Dear Maintainer,

For a few years now I've noticed errors like this in dmesg output:

Today I finally decided to look into this. It looks like amd64-microcode installs
the appropriate firmware for my system in /lib/firmware/amd/amd_sev_fam17h_model3xh.sbin
but the system does not understand it applies.

The linux-firmware.git commit message[1] says:

Armed with this information, I symlinked amd_sev_fam17h_model31h.sbin to
amd_sev_fam17h_model3xh.sbin and it now loads up fine:

As a fix for this issue, would it make sense for amd64-microcode to include
symlinks for all of the possible model numbers (0-f for each 'x' in the file name)?

Thank you!
Marko

[1]: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=9ee52be785cf91fc6a3c6aa27d484873f8270b72

It seems nothing will make you understand an issue faster than filing your first ever Debian bug about it :)

I noticed just now that the firmware loading *will* fall back to the correct file, it just happens after it has emitted the error lines:

This is made somewhat more difficult to notice by the error lines being highlighted and the lines indicating success not. So while my proposed symlinks do eliminate the error output in red, they wouldn’t affect actual functionality.

I think this issue can be closed.

AFAICT this is actually https://bugs.debian.org/1040738, which makes it a
kernel bug. As the maintainer has reassigned/merged #1051635 into this one
and thus to the amd64-microcode package, I'll leave reassigning it to src:linux
over to (one of) the maintainer(s).

Bug 1040738 has been fixed in kernel 6.9.2-1~exp1, which means you should no
longer receive those firmware error messages when they aren't actual errors.

Cheers,
  Diederik