Discussion:
[CFT] AMD cpu microcode update port sysutils/devcpu-data D13832
(too old to reply)
Sean Bruno
2018-01-11 23:03:15 UTC
Permalink
https://reviews.freebsd.org/D13832 <--- test this update

I'd like to get some feedback from AMD cpu users on this update. I've
restructured and undone a few things that may have been keeping folks
using this port from getting their runtime cpu microcode updates.

After installing the port, grab your microcode version via
sysutils/x86info. If you don't see an update, that only means there is
no update available for your system.

x86info -a | grep Microcode

Run the microcode_update and repeat. Check /var/log/messages for a
notification that the code was updated. You should be able to get
something like the following for your system if it executed an update:

***@lab:/home/sbruno # x86info -a | grep "CPU Model"
CPU Model (x86info's best guess): AMD FX Series Processor (OR-B2)

***@lab:/home/sbruno # x86info -a | grep Microcode
Microcode patch level: 0x6000629

***@lab:/home/sbruno # /usr/local/etc/rc.d/microcode_update onestart
Updating CPU Microcode...
Done.

***@lab:/home/sbruno # x86info -a | grep Microcode
Microcode patch level: 0x600063d

***@lab:/home/sbruno # grep microcode_update /var/log/messages
Jan 10 16:52:26 lab microcode_update:
/usr/local/share/cpucontrol/microcode_amd_fam15h.bin: updating cpu
/dev/cpuctl0 to revision 0x600063d... done.
Rainer Hurling
2018-01-12 11:49:15 UTC
Permalink
Post by Sean Bruno
https://reviews.freebsd.org/D13832 <--- test this update
I'd like to get some feedback from AMD cpu users on this update. I've
restructured and undone a few things that may have been keeping folks
using this port from getting their runtime cpu microcode updates.
After installing the port, grab your microcode version via
sysutils/x86info. If you don't see an update, that only means there is
no update available for your system.
x86info -a | grep Microcode
Run the microcode_update and repeat. Check /var/log/messages for a
notification that the code was updated. You should be able to get
CPU Model (x86info's best guess): AMD FX Series Processor (OR-B2)
Microcode patch level: 0x6000629
Updating CPU Microcode...
Done.
Microcode patch level: 0x600063d
/usr/local/share/cpucontrol/microcode_amd_fam15h.bin: updating cpu
/dev/cpuctl0 to revision 0x600063d... done.
Just for the record, for an older Phenom with dmesg:

CPU: AMD Phenom(tm) II X6 1090T Processor (3214.31-MHz K8-class CPU)
Origin="AuthenticAMD" Id=0x100fa0 Family=0x10 Model=0xa Stepping=0
Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
Features2=0x802009<SSE3,MON,CX16,POPCNT>
AMD
Features=0xee500800<SYSCALL,NX,MMX+,FFXSR,Page1GB,RDTSCP,LM,3DNow!+,3DNow!>
AMD
Features2=0x37ff<LAHF,CMP,SVM,ExtAPIC,CR8,ABM,SSE4A,MAS,Prefetch,OSVW,IBS,SKINIT,WDT>
SVM: NP,NRIP,NAsids=64
TSC: P-state invariant, performance statistics


#x86info -a | grep "CPU Model"
CPU Model (x86info's best guess): Phenom/Athlon/Sempron/Turion
(II)/Opteron (PH-E0)

#x86info -a | grep Microcode
Microcode patch level: 0x10000bf

#/usr/local/etc/rc.d/microcode_update onestart
Updating CPU Microcode...
Done.

#x86info -a | grep Microcode
Microcode patch level: 0x10000bf

#grep microcode_update /var/log/messages
---

So no recent update and no log messages, as expected ;)

Regards,
Rainer Hurling
Sean Bruno
2018-01-12 16:59:44 UTC
Permalink
Post by Rainer Hurling
Post by Sean Bruno
https://reviews.freebsd.org/D13832 <--- test this update
I'd like to get some feedback from AMD cpu users on this update. I've
restructured and undone a few things that may have been keeping folks
using this port from getting their runtime cpu microcode updates.
After installing the port, grab your microcode version via
sysutils/x86info. If you don't see an update, that only means there is
no update available for your system.
x86info -a | grep Microcode
Run the microcode_update and repeat. Check /var/log/messages for a
notification that the code was updated. You should be able to get
CPU Model (x86info's best guess): AMD FX Series Processor (OR-B2)
Microcode patch level: 0x6000629
Updating CPU Microcode...
Done.
Microcode patch level: 0x600063d
/usr/local/share/cpucontrol/microcode_amd_fam15h.bin: updating cpu
/dev/cpuctl0 to revision 0x600063d... done.
CPU: AMD Phenom(tm) II X6 1090T Processor (3214.31-MHz K8-class CPU)
Origin="AuthenticAMD" Id=0x100fa0 Family=0x10 Model=0xa Stepping=0
Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
Features2=0x802009<SSE3,MON,CX16,POPCNT>
AMD
Features=0xee500800<SYSCALL,NX,MMX+,FFXSR,Page1GB,RDTSCP,LM,3DNow!+,3DNow!>
AMD
Features2=0x37ff<LAHF,CMP,SVM,ExtAPIC,CR8,ABM,SSE4A,MAS,Prefetch,OSVW,IBS,SKINIT,WDT>
SVM: NP,NRIP,NAsids=64
TSC: P-state invariant, performance statistics
#x86info -a | grep "CPU Model"
CPU Model (x86info's best guess): Phenom/Athlon/Sempron/Turion
(II)/Opteron (PH-E0)
#x86info -a | grep Microcode
Microcode patch level: 0x10000bf
#/usr/local/etc/rc.d/microcode_update onestart
Updating CPU Microcode...
Done.
#x86info -a | grep Microcode
Microcode patch level: 0x10000bf
#grep microcode_update /var/log/messages
---
So no recent update and no log messages, as expected ;)
Regards,
Rainer Hurling
Thank you!

sean
Mike Tancsa
2018-01-12 15:38:17 UTC
Permalink
Post by Sean Bruno
https://reviews.freebsd.org/D13832 <--- test this update
I'd like to get some feedback from AMD cpu users on this update. I've
restructured and undone a few things that may have been keeping folks
using this port from getting their runtime cpu microcode updates.
Hi,
I am trying out on RELENG_11 on a Ryzen CPU

Without kib's commits at

https://lists.freebsd.org/pipermail/svn-src-stable-11/2018-January/005320.html

I get

***@testamd:/usr/ports/sysutils/devcpu-data #
/usr/local/etc/rc.d/microcode_update onestart
Updating CPU Microcode...
Re-evalutation of CPU flags Failed.
***@testamd:/usr/ports/sysutils/devcpu-data #

with r327597,

***@testamd:/home/mdtancsa # /usr/local/etc/rc.d/microcode_update onestart
Updating CPU Microcode...
Done.
***@testamd:/home/mdtancsa #



running x86info -a also generates this error / warning ?

CPU0: local APIC error 0x80


***@testamd:/home/mdtancsa # x86info -a | grep -i microco
Microcode patch level: 0x8001129
***@testamd:/home/mdtancsa # x86info -a | head -20
x86info v1.31pre
Unknown CPU family: 0x17
Unknown CPU family: 0x17
Unknown CPU family: 0x17
Unknown CPU family: 0x17
Unknown CPU family: 0x17
Unknown CPU family: 0x17
Unknown CPU family: 0x17
Unknown CPU family: 0x17
Unknown CPU family: 0x17
Unknown CPU family: 0x17
Unknown CPU family: 0x17
Unknown CPU family: 0x17
Found 12 identical CPUs
Extended Family: 8 Extended Model: 0 Family: 15 Model: 1 Stepping: 1
CPU Model (x86info's best guess):
Processor name string (BIOS programmed): AMD Ryzen 5 1600X Six-Core
Processor

Number of reporting banks : 7

***@testamd:/home/mdtancsa #


Also your diff is based on a previous version of the port. There was an
update since, with new microcode from Intel that gets clobbered in your
diffs.


Thanks!

---Mike
--
-------------------
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, ***@sentex.net
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada http://www.tancsa.com/
Sean Bruno
2018-01-12 16:58:27 UTC
Permalink
Post by Mike Tancsa
Post by Sean Bruno
https://reviews.freebsd.org/D13832 <--- test this update
I'd like to get some feedback from AMD cpu users on this update. I've
restructured and undone a few things that may have been keeping folks
using this port from getting their runtime cpu microcode updates.
Hi,
I am trying out on RELENG_11 on a Ryzen CPU
Without kib's commits at
https://lists.freebsd.org/pipermail/svn-src-stable-11/2018-January/005320.html
I get
/usr/local/etc/rc.d/microcode_update onestart
Updating CPU Microcode...
Re-evalutation of CPU flags Failed.
Correct, this is expected.
Post by Mike Tancsa
with r327597,
Updating CPU Microcode...
Done.
running x86info -a also generates this error / warning ?
CPU0: local APIC error 0x80
Probably, update your port of x86info. I pushed an update for this and
it might work better for you.
Post by Mike Tancsa
Microcode patch level: 0x8001129
x86info v1.31pre
Unknown CPU family: 0x17
Unknown CPU family: 0x17
Unknown CPU family: 0x17
Unknown CPU family: 0x17
Unknown CPU family: 0x17
Unknown CPU family: 0x17
Unknown CPU family: 0x17
Unknown CPU family: 0x17
Unknown CPU family: 0x17
Unknown CPU family: 0x17
Unknown CPU family: 0x17
Unknown CPU family: 0x17
Found 12 identical CPUs
Extended Family: 8 Extended Model: 0 Family: 15 Model: 1 Stepping: 1
Processor name string (BIOS programmed): AMD Ryzen 5 1600X Six-Core
Processor
Number of reporting banks : 7
Also your diff is based on a previous version of the port. There was an
update since, with new microcode from Intel that gets clobbered in your
diffs.
The update to Intel microcode was reverted. So, possibly the tree you
are using is out of date?

sean
Mike Tancsa
2018-01-12 17:12:31 UTC
Permalink
Post by Sean Bruno
Probably, update your port of x86info. I pushed an update for this and
it might work better for you.
Thanks, I tried it but still generates the error / warning. What does it
mean ? (CPU0: local APIC error 0x80)

It does however get rid of the "Unknown CPU family" error.

***@testamd:/usr/ports/sysutils/devcpu-data # x86info -a | head
x86info v1.31pre
Found 12 identical CPUs
Extended Family: 8 Extended Model: 0 Family: 15 Model: 1 Stepping: 1
CPU Model (x86info's best guess): AMD Zen Series Processor (ZP-B1)
Processor name string (BIOS programmed): AMD Ryzen 5 1600X Six-Core
Processor

Number of reporting banks : 7

MCG_CTL:
Data cache check enabled
Post by Sean Bruno
Post by Mike Tancsa
Also your diff is based on a previous version of the port. There was an
update since, with new microcode from Intel that gets clobbered in your
diffs.
The update to Intel microcode was reverted. So, possibly the tree you
are using is out of date?
Ahh, yes. I must have grabbed the ports just before you backed it out

https://lists.freebsd.org/pipermail/svn-ports-all/2018-January/171209.html

Thanks!

---Mike
--
-------------------
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, ***@sentex.net
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada http://www.tancsa.com/
Konstantin Belousov
2018-01-12 17:36:05 UTC
Permalink
Post by Mike Tancsa
Post by Sean Bruno
Probably, update your port of x86info. I pushed an update for this and
it might work better for you.
Thanks, I tried it but still generates the error / warning. What does it
mean ? (CPU0: local APIC error 0x80)
It means that the x86info accessed not implemented LAPIC register.
This warning is mostly harmless.
Jakub Lach
2018-01-15 00:01:22 UTC
Permalink
How far it's supposed to support legacy CPUs
on FreeBSD?

x86info

Found 2 identical CPUs
Extended Family: 0 Extended Model: 1 Family: 6 Model: 23 Stepping: 10
Type: 0 (Original OEM)
CPU Model (x86info's best guess): Unknown model.
Processor name string (BIOS programmed): Intel(R) Core(TM)2 Duo CPU
P9700 @ 2.80GHz

from README

"Features:
- SMP support.
- Recognition of all Intel/AMD/Centaur/Cyrix/VIA CPUs."




--
Sent from: http://freebsd.1045724.x6.nabble.com/freebsd-current-f3875308.html
Loading...