On 01/12/18 08:38, Mike Tancsa wrote: > On 1/11/2018 6:03 PM, Sean Bruno wrote: >> 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 > > root_at_testamd:/usr/ports/sysutils/devcpu-data # > /usr/local/etc/rc.d/microcode_update onestart > Updating CPU Microcode... > Re-evalutation of CPU flags Failed. > root_at_testamd:/usr/ports/sysutils/devcpu-data # Correct, this is expected. > > with r327597, > > root_at_testamd:/home/mdtancsa # /usr/local/etc/rc.d/microcode_update onestart > Updating CPU Microcode... > Done. > root_at_testamd:/home/mdtancsa # > > > > 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. > root_at_testamd:/home/mdtancsa # x86info -a | grep -i microco > Microcode patch level: 0x8001129 > root_at_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 > > root_at_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. > > The update to Intel microcode was reverted. So, possibly the tree you are using is out of date? sean
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:14 UTC