On Mon, 29 Feb 2016, Jiri Slaby wrote: > On 02/26/2016, 08:59 PM, Robert Święcki wrote: > > It happens only with 0x6000832 ucode, and Piledriver-based CPUs: i.e. > > newer AMD FX, and Opteron 300 series (4300, 6300 etc.). > > Ok, I can confirm this is: > AMD Opteron(tm) Processor 6348 > > And: > microcode: CPU0: patch_level=0x06000836 > > Thank all the interested parties! Jiri, does microcode 0x6000836 *fix* the erratum in microcode 0x6000832? Or did you mean both 0x6000832 and 0x6000836 have the same erratum discussed in this thread? -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html