> > un-applied. > > > > Even if deleting the blacklist entries were correct, > > which it more or less may be, the bug at hand is that > > "acpi=ht" is now broken -- whether invoked via DMI > > or cmdline; and this patch doesn't fix that. > > Indeed it doesn't. But the report also noted that the system worked fine > with acpi=force, so this is something that we should clean up regardless > of the original bug. I fixed the acpi=ht option, and also removed the system at hand from the blacklist. This is what 2.6.33 and 2.6.32.stable need. In the future, I'll consider deleting the "acpi=ht" option all together, and the blacklist with it, but such changes are always harder than expected. On a related topic, we should probably consider bringing back the "noht" option. However we would do so by checking the APIC-id topology rather than assuming any consistency in how the BIOS enumerates the processors. thanks, -Len Brown, Intel Open Source Technology Center -- 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
