https://bugzilla.kernel.org/show_bug.cgi?id=117301 --- Comment #3 from piotr.pejas@xxxxxxxxx --- Thank you for your attention to this matter. I have latest BIOS. Unfortunately I can not find CHANGELOG so I don't know if G0 steeping (SLAEG) is supported and does what is needed for proper initialization. DMI: Apple Computer, Inc. MacPro2,1/Mac-F4208DC8, BIOS MP21.88Z.007F.B06.0707021348 07/02/07 I've got linux early microcode update to update both cpu's: # dmesg | grep microcode [ 0.000000] CPU0 microcode updated early to revision 0x6b, date = 2010-10-02 [ 0.056030] CPU1 microcode updated early to revision 0x6b, date = 2010-10-02 [ 0.068270] CPU2 microcode updated early to revision 0x6b, date = 2010-10-02 [ 0.081025] CPU3 microcode updated early to revision 0x6b, date = 2010-10-02 [ 0.093019] CPU4 microcode updated early to revision 0xbc, date = 2010-10-03 [ 0.170019] CPU5 microcode updated early to revision 0xbc, date = 2010-10-03 [ 0.187019] CPU6 microcode updated early to revision 0xbc, date = 2010-10-03 [ 0.204019] CPU7 microcode updated early to revision 0xbc, date = 2010-10-03 [ 0.710545] microcode: CPU0 sig=0x6f7, pf=0x40, revision=0x6b [ 0.710555] microcode: CPU1 sig=0x6f7, pf=0x40, revision=0x6b [ 0.710565] microcode: CPU2 sig=0x6f7, pf=0x40, revision=0x6b [ 0.710577] microcode: CPU3 sig=0x6f7, pf=0x40, revision=0x6b [ 0.710588] microcode: CPU4 sig=0x6fb, pf=0x40, revision=0xbc [ 0.710600] microcode: CPU5 sig=0x6fb, pf=0x40, revision=0xbc [ 0.710611] microcode: CPU6 sig=0x6fb, pf=0x40, revision=0xbc [ 0.710623] microcode: CPU7 sig=0x6fb, pf=0x40, revision=0xbc [ 0.710670] microcode: Microcode Update Driver: v2.00 <tigran@xxxxxxxxxxxxxxxxxxxx>, Peter Oruba via intel-ucode.img https://wiki.archlinux.org/index.php/microcode but problem persists: [ 103.470656] kvm: CPU 0 feature inconsistency! I will replace one CPU too match steeping of the second one, probably will go with G0 those are easily available and quiet inexpensive. Thank you. PS IMO we can close this bug -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
