Hi @
Welsper, thanks for your dual-xeon version, but I highly suspect some race conditions/other bugs in it. I'm able to hit stable 29x on a single socket with the original V3, but results vary from run to run with your V3_2 (from 25x mult on all cores to global freeze upon microcode update). So, I've tried latest V3_2_39, and got the following after boot:
[ 2.331167] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x39
[ 2.331177] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331187] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331196] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331206] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331215] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331225] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331235] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331245] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331254] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331264] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331274] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331284] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331295] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331306] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x39
[ 2.331316] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331323] microcode: CPU16 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331331] microcode: CPU17 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331341] microcode: CPU18 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331350] microcode: CPU19 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331359] microcode: CPU20 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331368] microcode: CPU21 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331378] microcode: CPU22 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331386] microcode: CPU23 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331396] microcode: CPU24 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331405] microcode: CPU25 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331414] microcode: CPU26 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331424] microcode: CPU27 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331433] microcode: CPU28 sig=0x306f2, pf=0x1, revision=0x39
[ 2.331441] microcode: CPU29 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331450] microcode: CPU30 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331459] microcode: CPU31 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331467] microcode: CPU32 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331476] microcode: CPU33 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331485] microcode: CPU34 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331494] microcode: CPU35 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331504] microcode: CPU36 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331512] microcode: CPU37 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331521] microcode: CPU38 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331530] microcode: CPU39 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331539] microcode: CPU40 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331548] microcode: CPU41 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331557] microcode: CPU42 sig=0x306f2, pf=0x1, revision=0x39
[ 2.331564] microcode: CPU43 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331573] microcode: CPU44 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331582] microcode: CPU45 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331591] microcode: CPU46 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331599] microcode: CPU47 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331607] microcode: CPU48 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331615] microcode: CPU49 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331623] microcode: CPU50 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331631] microcode: CPU51 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331639] microcode: CPU52 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331647] microcode: CPU53 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331656] microcode: CPU54 sig=0x306f2, pf=0x1, revision=0x0
[ 2.331664] microcode: CPU55 sig=0x306f2, pf=0x1, revision=0x0
Only 4 cores got theirs microcode update, and, I suspect, all other hacks too. FYI, this is a dual e5-2683 with 2x14x2 topology.