From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] AMD microcode updates - where are they?!
Date: Fri, 12 Jul 2019 13:18:10 +0100 [thread overview]
Message-ID: <5488074.erHLfLloyy@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 1484 bytes --]
I'm looking at dmesg output which on my Intel CPUS of various vintages shows
"microcode updated early ..." but two different AMD APUs of mine do not show
the same, despite AMD apparently releasing microcode updates going back to
2011:
https://www.bleepingcomputer.com/news/hardware/amd-releases-spectre-v2-microcode-updates-for-cpus-going-back-to-2011/
I have observed OEMs for laptop MoBos rarely if ever bother to release a UEFI/
BIOS firmware update past 1-2 years from launch of their products, while
desktop OEMs may keep releasing updates for 3-5 years.
Since there are no OEM MoBo firmware releases and I see no "microcode updated
early ..." message in dmesg, I thought of checking with other Gentoo users if
I'm doing something wrong, or if this is a common observation for AMD CPU/
APUs?
PS. I include the microcode in the kernel, for both my Intel and AMD systems,
rather than use an initramfs; e.g.
CONFIG_EXTRA_FIRMWARE="amd-ucode/microcode_amd_fam15h.bin ..."
PPS. This is all shown on one of the AMD APUs, way down during the booting
process:
$ dmesg | grep -i micro
[ 0.622441] [drm] Loading ARUBA Microcode
[ 5.763242] [drm] Loading hainan Microcode
[ 6.653025] microcode: CPU0: patch_level=0x06001119
[ 6.657962] microcode: CPU1: patch_level=0x06001119
[ 6.658890] microcode: CPU2: patch_level=0x06001119
[ 6.659881] microcode: CPU3: patch_level=0x06001119
[ 6.661136] microcode: Microcode Update Driver: v2.2.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2019-07-12 12:20 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 12:18 Mick [this message]
2019-07-12 16:07 ` [gentoo-user] Re: AMD microcode updates - where are they?! Ian Zimmerman
2019-07-13 0:56 ` Adam Carter
2019-07-13 1:13 ` Adam Carter
2019-07-13 10:04 ` Mick
2019-07-13 10:01 ` Mick
2019-07-13 16:21 ` [gentoo-user] " Jack
2019-07-13 17:18 ` Mick
2019-07-13 17:23 ` Mick
2019-07-13 17:42 ` Jack
2019-07-13 18:06 ` Mick
2019-07-13 18:16 ` Corbin
2019-07-13 19:23 ` Mick
2019-07-13 20:16 ` Wols Lists
2019-07-13 21:01 ` Rich Freeman
2019-07-13 22:03 ` Mick
2019-07-14 13:26 ` Mick
2019-07-15 0:42 ` Adam Carter
2019-07-17 3:21 ` Corbin
2019-07-17 10:58 ` Mick
2019-07-17 12:46 ` Corbin
2019-07-17 20:51 ` [gentoo-user] " Ian Zimmerman
2019-07-18 12:33 ` Corbin
2019-07-18 18:23 ` Mick
2019-07-17 23:38 ` [gentoo-user] " Adam Carter
2019-07-15 4:30 ` [gentoo-user] " Ian Zimmerman
2019-07-15 21:18 ` Ian Zimmerman
2019-07-16 9:47 ` Mick
2019-07-15 5:15 ` [gentoo-user] " Adam Carter
2019-07-16 8:10 ` Neil Bothwick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5488074.erHLfLloyy@localhost \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox