Just realized the message below doesn't end up on debian-kernel@l.d.o but as I think it *is* a kernel bug, forwarding it there. ---------- Forwarded Message ---------- Subject: Re: Bug#1043273: amd64-microcode: AMD SEV firmware files not loaded on matching systems Date: dinsdag 12 september 2023, 01:23:05 CEST From: Diederik de Haas <didi.debian@cknow.org> To: 1043273@bugs.debian.org On Tue, 8 Aug 2023 13:41:56 +0300 Marko Karppinen <marko@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 > > 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). -----------------------------------------
Attachment:
signature.asc
Description: This is a digitally signed message part.