Re: Problem with late AMD microcode reload/feedback

2018-12-16 Thread Borislav Petkov
On Sun, Dec 16, 2018 at 12:02:49PM +0100, Rafał Miłecki wrote: > OK, if you say so, I'll try not to panic seeing those errors repeating > over and over. Yes, patience is the key :-) > I know such issues may take months or years to get fixed, so I was > trying to do some hacking on my own. I'll tr

Re: Problem with late AMD microcode reload/feedback

2018-12-16 Thread Rafał Miłecki
On Sun, 16 Dec 2018 at 11:44, Borislav Petkov wrote: > On Sun, Dec 16, 2018 at 11:26:29AM +0100, Rafał Miłecki wrote: > > Debugging CPU errors. > > I told you that this issue is being worked on and there will be a fix > of sorts at some point. Don't try any funky business of downgrading the > micr

Re: Problem with late AMD microcode reload/feedback

2018-12-16 Thread Borislav Petkov
On Sun, Dec 16, 2018 at 11:26:29AM +0100, Rafał Miłecki wrote: > Debugging CPU errors. I told you that this issue is being worked on and there will be a fix of sorts at some point. Don't try any funky business of downgrading the microcode and maybe break your boxes in the process. Just ignore the

Re: Problem with late AMD microcode reload/feedback

2018-12-16 Thread Rafał Miłecki
On Sun, 16 Dec 2018 at 11:06, Borislav Petkov wrote: > > For my hack tests I'd like to replace my 0x0810100b with a 0x08101007. > > Why would you even want to downgrade the microcode?! Debugging CPU errors. I have two notebooks: 1) HP EliteBook 745 G5 with Ryzen 5 PRO 2500U It runs 1.03.01 BIOS

Re: Problem with late AMD microcode reload/feedback

2018-12-16 Thread Borislav Petkov
On Sun, Dec 16, 2018 at 09:08:00AM +0100, Rafał Miłecki wrote: > Thanks! I had no idea microcode_amd_fam17h.bin is a container with few > microcodes. I thought there is a single microcode for a whole family > (e.g. 17h). It is a container for all F17h - you're simply making the wrong assumption th

Re: Problem with late AMD microcode reload/feedback

2018-12-16 Thread Rafał Miłecki
On 16.12.2018 01:05, Borislav Petkov wrote: On Sun, Dec 16, 2018 at 12:46:05AM +0100, Rafał Miłecki wrote: [19.736770] microcode: [find_equiv_id] sig:8458000 That's your CPU's family/model/stepping: 0x0810f10 [19.736772] microcode: [find_equiv_id] equiv_table->installed_cpu:8392466 [19.73677

Re: Problem with late AMD microcode reload/feedback

2018-12-15 Thread Borislav Petkov
On Sun, Dec 16, 2018 at 12:46:05AM +0100, Rafał Miłecki wrote: > I'm trying to reload AMD Ryzen Mobile (fam17h) microcode doing: > echo 1 > /sys/devices/system/cpu/microcode/reload Also, I'd advise against using the late loading method but put the microcode in the initrd (which your distro should

Re: Problem with late AMD microcode reload/feedback

2018-12-15 Thread Borislav Petkov
On Sun, Dec 16, 2018 at 12:46:05AM +0100, Rafał Miłecki wrote: > [19.736770] microcode: [find_equiv_id] sig:8458000 That's your CPU's family/model/stepping: 0x0810f10 > [19.736772] microcode: [find_equiv_id] equiv_table->installed_cpu:8392466 > [19.736775] microcode: [find_equiv_id] equiv_table->

Problem with late AMD microcode reload/feedback

2018-12-15 Thread Rafał Miłecki
Hi, I'm trying to reload AMD Ryzen Mobile (fam17h) microcode doing: echo 1 > /sys/devices/system/cpu/microcode/reload The problem is I don't get any feedback. No error for the "echo" command, no a single new line in the "dmesg". I have no idea if microcode has been reloaded or not. I did a quick