Re: Please add AMD-SEV firmware files (amd-folder) to close CVE-2019-9836 on specific EPYC-CPUs
On Tue, 26 Jan 2021, Debian Bug Tracking System wrote:
> > reassign 970395 amd64-microcode
> Bug #970395 [src:firmware-nonfree] firmware-nonfree: Please add AMD-SEV firmware files (amd-folder) to close CVE-2019-9836 on specific EPYC-CPUs
> Bug reassigned from package 'src:firmware-nonfree' to 'amd64-microcode'.
> Ignoring request to alter found versions of bug #970395 to the same values previously set
> Ignoring request to alter fixed versions of bug #970395 to the same values previously set
> > # please update to latest bc9cd0b7b0e96038ccc041ff409948d8f176142d
> > # 20/11/2020 in linux-firmware
> > done
> Unknown command or malformed arguments to command.
> > bc9cd0b7b0e96038ccc041ff409948d8f176142d has:
> Unknown command or malformed arguments to command.
> > Update AMD SEV firmware to version 0.17 build 44 for AMD family 17h
> Unknown command or malformed arguments to command.
> > processors with models in the range 00h to 0fh.
> Unknown command or malformed arguments to command.
> > Update AMD SEV firmware to version 0.24 build 7 for AMD family 17h
> Unknown command or malformed arguments to command.
> Too many unknown commands, stopping here.
I will look into this soon, probably this weekend.
I will direct any questions I have to the submitters and to this bug
report.
However, I have to find out if these firmware data files should go into
the early initramfs like the microcode (and *how*: naming, packaging
into a single file? the early initramfs works differently than normal
firmware loading). Or should it go into the normal initramfs ? Or
both?
If you have the answer to these questions and can follow up with them,
it will hasten the fix since I will not have to spend time looking for
the answers.
--
Henrique Holschuh
Reply to: