From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: AMD microcode updates - where are they?!
Date: Sat, 13 Jul 2019 11:01:56 +0100 [thread overview]
Message-ID: <6206681.QGZE5AxUjX@localhost> (raw)
In-Reply-To: <CAC=wYCHCOuvfDFOPCz1aRtS9XpAoU3oBUhoxcFFAydWp0xu6Kw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 5325 bytes --]
Thank you both, for your replies.
On Saturday, 13 July 2019 01:56:30 BST Adam Carter wrote:
> > > $ 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.
> >
> > I have a similar experience:
> >
> > [ 0.659996] microcode: CPU0: patch_level=0x010000c8
> > [ 0.660001] microcode: CPU1: patch_level=0x010000c8
> > [ 0.660006] microcode: CPU2: patch_level=0x010000c8
> > [ 0.660011] microcode: CPU3: patch_level=0x010000c8
> > [ 0.660029] microcode: Microcode Update Driver: v2.2.
> > [ 7.853509] [drm] Loading RS780 Microcode
> >
> > I have a 10h generation processor, and I also build in microcode_amd.bin
> > with the kernel.
I had not until now built in 'amd-ucode/microcode_amd.bin', only 'amd-ucode/
microcode_amd_fam15h.bin', because this laptop has a 15h family CPU:
# lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
Address sizes: 48 bits physical, 48 bits virtual
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 2
Core(s) per socket: 2
Socket(s): 1
NUMA node(s): 1
Vendor ID: AuthenticAMD
CPU family: 21
Model: 19
Model name: AMD A10-5750M APU with Radeon(tm) HD Graphics
Stepping: 1
CPU MHz: 1330.218
CPU max MHz: 2500.0000
CPU min MHz: 1400.0000
BogoMIPS: 4990.70
Virtualization: AMD-V
L1d cache: 16K
L1i cache: 64K
L2 cache: 2048K
NUMA node0 CPU(s): 0-3
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb
rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf
pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave avx f16c
lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch
osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core
perfctr_nb cpb hw_pstate ssbd vmmcall bmi1 arat npt lbrv svm_lock nrip_save
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold
$ dmesg | grep family:
[ 0.291910] smpboot: CPU0: AMD A10-5750M APU with Radeon(tm) HD Graphics
(family: 0x15, model: 0x13, stepping: 0x1)
> Piledriver gets the early message barcelona/fam10h doesnt;
>
> # dmesg | grep microc
> [ 1.663099] microcode: microcode updated early to new
> patch_level=0x06000852
> [ 1.664161] microcode: CPU0: patch_level=0x06000852
> [ 1.665147] microcode: CPU1: patch_level=0x06000852
> [ 1.666135] microcode: CPU2: patch_level=0x06000852
> [ 1.667119] microcode: CPU3: patch_level=0x06000852
> [ 1.668034] microcode: CPU4: patch_level=0x06000852
> [ 1.668955] microcode: CPU5: patch_level=0x06000852
> [ 1.670060] microcode: CPU6: patch_level=0x06000852
> [ 1.670985] microcode: CPU7: patch_level=0x06000852
> [ 1.672012] microcode: Microcode Update Driver: v2.2.
OK, mine is also a Piledriver (mobile) CPU according to these tables:
https://en.wikichip.org/wiki/amd/a10
However, I don't see any early microcode being loaded. :-/
I added 'amd-ucode/microcode_amd.bin' in the kernel, just in case it was
needed and rebooted, but still no difference.
> # dmesg | grep microc
> [ 1.700378] microcode: CPU0: patch_level=0x010000c8
> [ 1.700435] microcode: CPU1: patch_level=0x010000c8
> [ 1.700488] microcode: CPU2: patch_level=0x010000c8
> [ 1.700543] microcode: CPU3: patch_level=0x010000c8
> [ 1.700684] microcode: Microcode Update Driver: v2.2.
>
> microcode_amd.bin hasn't changed since at least January 2018, so maybe
> there hasnt been any updates for the recent CPU vulnerabilities.
>
> Assuming the numbering is sequential its odd that the APU is at 0x06001119
> but the latest from linux-firmware is only 0x010000c8. Are you sure the APU
> is not fam16h ?
Yes, positive. As I've shown above the laptop has an A10 fam15h mobile
Piledriver processor.
The desktop has an A10 Steamroller, Kaveri APU:
$ dmesg | grep family:
[ 0.269754] smpboot: CPU0: AMD A10-7850K Radeon R7, 12 Compute Cores 4C+8G
(family: 0x15, model: 0x30, stepping: 0x1)
It has the 'amd-ucode/microcode_amd_fam15h.bin' built in the kernel and it
also shows no early microcode being loaded:
$ dmesg | grep micro
[ 1.578553] microcode: CPU0: patch_level=0x06003106
[ 1.579338] microcode: CPU1: patch_level=0x06003106
[ 1.580943] microcode: CPU2: patch_level=0x06003106
[ 1.581729] microcode: CPU3: patch_level=0x06003106
[ 1.582608] microcode: Microcode Update Driver: v2.2.
Notice the patch number is slightly higher than the laptop's, which can be
explained by the fact the desktop's Steamroller was launched in Jan 2014,
while the laptop's Piledriver was launched in March 2013.
Anyway, this does not explain why your Piledriver at least is loading early
the microcode, but mine isn't. :-/
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-07-13 10:02 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 12:18 [gentoo-user] AMD microcode updates - where are they?! Mick
2019-07-12 16:07 ` [gentoo-user] " 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 [this message]
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=6206681.QGZE5AxUjX@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