summaryrefslogtreecommitdiffstats
path: root/amd-ucode/README
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2024-04-28 09:10:08 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2024-04-28 09:10:08 +0000
commit74f64333251c68f9144f541ba02dac264413ee02 (patch)
tree65897847ccc65ec9c18f271ca4bf7876588f4dff /amd-ucode/README
parentInitial commit. (diff)
downloadamd64-microcode-74f64333251c68f9144f541ba02dac264413ee02.tar.xz
amd64-microcode-74f64333251c68f9144f541ba02dac264413ee02.zip
Adding upstream version 3.20230808.1.1~deb12u1.upstream/3.20230808.1.1_deb12u1upstream
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'amd-ucode/README')
-rw-r--r--amd-ucode/README55
1 files changed, 55 insertions, 0 deletions
diff --git a/amd-ucode/README b/amd-ucode/README
new file mode 100644
index 0000000..fac1152
--- /dev/null
+++ b/amd-ucode/README
@@ -0,0 +1,55 @@
+This repository includes microcode container files for family 15h, 16h,
+17h, and 19h AMD CPUs. Microcode patches for families earlier than 15h are
+included in the microcode_amd.bin microcode container file. The microcode
+patches included in an AMD CPU microcode container file can be listed using
+the script in the following git repository:
+https://github.com/AMDESE/amd_ucode_info
+
+The microcode patches included in the container files in this directory are
+listed below:
+
+Microcode patches in microcode_amd.bin:
+ Family=0x10 Model=0x02 Stepping=0x02: Patch=0x01000083 Length=960 bytes
+ Family=0x10 Model=0x02 Stepping=0x0a: Patch=0x01000084 Length=960 bytes
+ Family=0x10 Model=0x06 Stepping=0x02: Patch=0x010000c7 Length=960 bytes
+ Family=0x10 Model=0x05 Stepping=0x03: Patch=0x010000c8 Length=960 bytes
+ Family=0x10 Model=0x09 Stepping=0x01: Patch=0x010000d9 Length=960 bytes
+ Family=0x10 Model=0x08 Stepping=0x00: Patch=0x010000da Length=960 bytes
+ Family=0x10 Model=0x05 Stepping=0x02: Patch=0x010000db Length=960 bytes
+ Family=0x10 Model=0x0a Stepping=0x00: Patch=0x010000dc Length=960 bytes
+ Family=0x11 Model=0x03 Stepping=0x01: Patch=0x02000032 Length=512 bytes
+ Family=0x12 Model=0x01 Stepping=0x00: Patch=0x03000027 Length=960 bytes
+ Family=0x14 Model=0x01 Stepping=0x00: Patch=0x05000029 Length=1568 bytes
+ Family=0x14 Model=0x02 Stepping=0x00: Patch=0x05000119 Length=1568 bytes
+
+Microcode patches in microcode_amd_fam15h.bin:
+ Family=0x15 Model=0x01 Stepping=0x02: Patch=0x0600063e Length=2592 bytes
+ Family=0x15 Model=0x02 Stepping=0x00: Patch=0x06000852 Length=2592 bytes
+ Family=0x15 Model=0x10 Stepping=0x01: Patch=0x06001119 Length=2592 bytes
+
+Microcode patches in microcode_amd_fam16h.bin:
+ Family=0x16 Model=0x00 Stepping=0x01: Patch=0x0700010f Length=3458 bytes
+
+Microcode patches in microcode_amd_fam17h.bin:
+ Family=0x17 Model=0x08 Stepping=0x02: Patch=0x0800820d Length=3200 bytes
+ Family=0x17 Model=0x31 Stepping=0x00: Patch=0x0830107a Length=3200 bytes
+ Family=0x17 Model=0xa0 Stepping=0x00: Patch=0x08a00008 Length=3200 bytes
+ Family=0x17 Model=0x01 Stepping=0x02: Patch=0x0800126e Length=3200 bytes
+
+Microcode patches in microcode_amd_fam19h.bin:
+ Family=0x19 Model=0x11 Stepping=0x01: Patch=0x0a10113e Length=5568 bytes
+ Family=0x19 Model=0x11 Stepping=0x02: Patch=0x0a10123e Length=5568 bytes
+ Family=0x19 Model=0xa0 Stepping=0x02: Patch=0x0aa00212 Length=5568 bytes
+ Family=0x19 Model=0x01 Stepping=0x01: Patch=0x0a0011d1 Length=5568 bytes
+ Family=0x19 Model=0x01 Stepping=0x00: Patch=0x0a001079 Length=5568 bytes
+ Family=0x19 Model=0x01 Stepping=0x02: Patch=0x0a001234 Length=5568 bytes
+ Family=0x19 Model=0xa0 Stepping=0x01: Patch=0x0aa00116 Length=5568 bytes
+
+NOTE: For Genoa (Family=0x19 Model=0x11) and Bergamo (Family=0x19 Model=0xa0),
+either AGESA version >= 1.0.0.8 OR a kernel with the following commit is
+required:
+a32b0f0db3f3 ("x86/microcode/AMD: Load late on both threads too")
+
+When late loading the patches for Genoa or Bergamo, there may be one spurious
+NMI observed per physical core. These NMIs are benign and don't cause any
+functional issue but will result in kernel messages being logged.