On 22 Jul 2024 11:52:36 +0200 Diederik de Haas <[email protected]> wrote:
> Package: amd64-microcode
> Version: 3.20240116.2+nmu1
> 
> I was testing with `rngtest` on arm64 devices and wanted to know the
> results on my amd64 AMD (Ryzen) CPU/APU.
> 
> System 1:
> CPU: AMD Ryzen 7 1800X Eight-Core Processor (family: 0x17, model: 0x1,
> stepping: 0x1)
> CPU family: 23 (in decimal)
> microcode revision: 0x08001138 (according to dmesg)
> 
> System 2:
> CPU/APU: AMD Ryzen 5 5500GT with Radeon Graphics (family: 0x19, model: 0x50,
> stepping: 0x0)
> CPU family: 25 (in decimal)
> microcode revision: 0x0a50000f (according to dmesg)
> 
> While `rngtest` results looked excellent on System 1, it revealed that
> the HWRNG on System 2 is broken.
> I'm currently triaging it (with Asus; MB manufacturer) and they asked me
> to test with the latest microcode. So hereby a '+1' on bug #1076128.
> 
> I am running the latest amd64-microcode package on both and looked
> further into all the package files and actually got confused.
> I got the *impression* that some heuristic was used to determine whether
> the microcode update should be applied.
> That impression was based on what I saw in ``/etc/default/amd64-microcode``
> and ``/etc/modprobe.d/amd64-microcode-blacklist.conf``.
> 
> I also went looking for the microcode revision number reported by
> ``dmesg`` in the upstream repo, but the relevant data seems to be part
> of ``/usr/share/doc/amd64-microcode/README.gz``.
> But no where did I find those microcode revision codes.
> 
> I'd like to know whether I'm actually running the latest microcode,
> but I haven't figured out a way how?
> So hereby a request to clarify/document how I (and others) can verify
> whether they're (actually) *running* the latest (amd64-)microcode.

I looked closely how previous updates were done and made a 20240710.1+nmu1
release myself and then used the .deb file created by Salsa's CI:
https://salsa.debian.org/diederik/amd64-microcode/-/commits/release-3.20240710.1+nmu1

Before:
root@cknowsvr04:~# dmesg | grep microcode
[    0.587262] microcode: Current revision: 0x0a50000f

root@cknowsvr04:~# apt install 
./amd64-microcode_3.20240710.1+nmu1+salsaci+20240723+2_amd64.deb 
Note, selecting 'amd64-microcode' instead of 
'./amd64-microcode_3.20240710.1+nmu1+salsaci+20240723+2_amd64.deb'

Upgrading:
  amd64-microcode

...
Setting up amd64-microcode (3.20240710.1+nmu1+salsaci+20240723+2) ...
update-initramfs: deferring update (trigger activated)
amd64-microcode: microcode will be updated at next boot
Processing triggers for initramfs-tools (0.142) ...
update-initramfs: Generating /boot/initrd.img-6.9.9-amd64
root@cknowsvr04:~# reboot

After:
root@cknowsvr04:~# dmesg | grep microcode
[    0.587102] microcode: Current revision: 0x0a50000f


I'm pretty sure I did the 'nmu' correctly, but it seems the microcode
update isn't applied (at all).

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to