On Tue, May 25, 2010 at 11:33:39AM -0400, Len Brown wrote: > So if we see a nehalem system that has BM_STS *always* set, > even when no devices are active in the system, my guess is > that the BIOS mis-configured the chip-set and we should > ignore that bit. If BM_STS is changing at run time, then > that is a more interesting situation, and we should endeavor > to find what device activity is changing it. Right. Determining that seems... awkward. FWIW, we've been shipping Luming's patch for several months now without anything obviously breaking in the process. This behaviour seems reasonably prevelant on Nehalem-EX systems. -- Matthew Garrett | mjg59@xxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
