Re: AMD EPYC microcode update bug?

2018-01-09 Thread Tom Lendacky
On 1/9/2018 5:06 PM, Gabriel C wrote: > 2018-01-09 23:47 GMT+01:00 Tom Lendacky : >> On 1/9/2018 4:28 PM, Gabriel C wrote: >>> Hello , >>> >>> I'm testing an EPYC system right now with 2 EPYC 7281 16-Core Processors. >>> >>> I'm on 4.15.0-rc7 and tested an update to

Re: AMD EPYC microcode update bug?

2018-01-09 Thread Tom Lendacky
On 1/9/2018 5:06 PM, Gabriel C wrote: > 2018-01-09 23:47 GMT+01:00 Tom Lendacky : >> On 1/9/2018 4:28 PM, Gabriel C wrote: >>> Hello , >>> >>> I'm testing an EPYC system right now with 2 EPYC 7281 16-Core Processors. >>> >>> I'm on 4.15.0-rc7 and tested an update to microcode_amd_fam17h.bin. >>>

Re: AMD EPYC microcode update bug?

2018-01-09 Thread Gabriel C
On 10.01.2018 00:06, Gabriel C wrote: 2018-01-09 23:47 GMT+01:00 Tom Lendacky : On 1/9/2018 4:28 PM, Gabriel C wrote: Hello , I'm testing an EPYC system right now with 2 EPYC 7281 16-Core Processors. I'm on 4.15.0-rc7 and tested an update to microcode_amd_fam17h.bin.

Re: AMD EPYC microcode update bug?

2018-01-09 Thread Gabriel C
On 10.01.2018 00:06, Gabriel C wrote: 2018-01-09 23:47 GMT+01:00 Tom Lendacky : On 1/9/2018 4:28 PM, Gabriel C wrote: Hello , I'm testing an EPYC system right now with 2 EPYC 7281 16-Core Processors. I'm on 4.15.0-rc7 and tested an update to microcode_amd_fam17h.bin. First run was made by

Re: AMD EPYC microcode update bug?

2018-01-09 Thread Gabriel C
2018-01-09 23:47 GMT+01:00 Tom Lendacky : > On 1/9/2018 4:28 PM, Gabriel C wrote: >> Hello , >> >> I'm testing an EPYC system right now with 2 EPYC 7281 16-Core Processors. >> >> I'm on 4.15.0-rc7 and tested an update to microcode_amd_fam17h.bin. >> >> First run was made

Re: AMD EPYC microcode update bug?

2018-01-09 Thread Gabriel C
2018-01-09 23:47 GMT+01:00 Tom Lendacky : > On 1/9/2018 4:28 PM, Gabriel C wrote: >> Hello , >> >> I'm testing an EPYC system right now with 2 EPYC 7281 16-Core Processors. >> >> I'm on 4.15.0-rc7 and tested an update to microcode_amd_fam17h.bin. >> >> First run was made by using the early

Re: AMD EPYC microcode update bug?

2018-01-09 Thread Tom Lendacky
On 1/9/2018 4:28 PM, Gabriel C wrote: > Hello , > > I'm testing an EPYC system right now with 2 EPYC 7281 16-Core Processors. > > I'm on 4.15.0-rc7 and tested an update to microcode_amd_fam17h.bin. > > First run was made by using the early microcode option with dracut[1] > so loading from a

Re: AMD EPYC microcode update bug?

2018-01-09 Thread Tom Lendacky
On 1/9/2018 4:28 PM, Gabriel C wrote: > Hello , > > I'm testing an EPYC system right now with 2 EPYC 7281 16-Core Processors. > > I'm on 4.15.0-rc7 and tested an update to microcode_amd_fam17h.bin. > > First run was made by using the early microcode option with dracut[1] > so loading from a

AMD EPYC microcode update bug?

2018-01-09 Thread Gabriel C
Hello , I'm testing an EPYC system right now with 2 EPYC 7281 16-Core Processors. I'm on 4.15.0-rc7 and tested an update to microcode_amd_fam17h.bin. First run was made by using the early microcode option with dracut[1] so loading from a initrd. the driver reported 63 updated CPUs while CPU0

AMD EPYC microcode update bug?

2018-01-09 Thread Gabriel C
Hello , I'm testing an EPYC system right now with 2 EPYC 7281 16-Core Processors. I'm on 4.15.0-rc7 and tested an update to microcode_amd_fam17h.bin. First run was made by using the early microcode option with dracut[1] so loading from a initrd. the driver reported 63 updated CPUs while CPU0