On Mon, 2009-08-10 at 11:06 -0700, Prarit Bhargava wrote: > > Dominik Brodowski wrote: > > BTW: the spec update says "Intel has not observed this erratum > > with any commercially available software, or system". So is this really an > > issue we should work around, even if the spec does not suggest any > > workaround? > > > > We (Red Hat) absolutely are seeing this behavior on a 7100 series > system. So, yes, this is something we should work around. > > FWIW, jvillalo@xxxxxxxxxx (cc'd on this email) is an Intel engineer who > works on-site at Red Hat and has signed off on this issue... > What is the specific Machine Check Error you are getting here? Is it processor specific error or memory/platform related? Thanks, Venki -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
