On Tuesday, 12 September 2023 01:23:05 CEST Diederik de Haas wrote: > On Tue, 8 Aug 2023 13:41:56 +0300 Marko Karppinen <ma...@karppinen.fi> wrote: > > 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: > > > [ 4.069026] ccp 0000:4a:00.1: firmware: failed to load > > > amd/amd_sev_fam17h_model31h.sbin (-2) [ 4.069293] firmware_class: > > > See https://wiki.debian.org/Firmware for information about missing > > > firmware [ 4.069597] ccp 0000:4a:00.1: firmware: failed to load > > > amd/amd_sev_fam17h_model31h.sbin (-2) [ 4.070002] ccp 0000:4a:00.1: > > > firmware: direct-loading firmware amd/amd_sev_fam17h_model3xh.sbin [ > > > 4.102461] ccp 0000:4a:00.1: SEV API:0.24 build:16 > > 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).
FYI (and now also with you in To): 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
signature.asc
Description: This is a digitally signed message part.
