On 09.11.2011 18:58, Konrad Rzeszutek Wilk wrote: > On Wed, Oct 26, 2011 at 03:57:15PM +0200, Stefan Bader wrote: >> On 26.10.2011 15:48, Konrad Rzeszutek Wilk wrote: >>>>> What about using the cpuidle_disabled() functionality and adhere to that? >>>>> As so: >>>>> >>> .. snip.. >>>> >>>> >From reading over it, this should work. Though I would be interested to hear >>>> from the linux-acpi folks. Also to double check that calling pm_idle when >>>> cpuidle.off was specified really is what is intended. >>> >>> Oh yeah, definitly need the input from linux-acpi folks. And also to be actually >>> tested :-) >> >> I can volunteer to do the testing. But I am lazy enough to hold back a bit as >> someone may tell us this is completely the wrong way to fix it. :) > > So the other option is to use 'idle=halt' on the Linux command line. That should > provide the workaround for the folks reporting this (is there a BZ for it?). > Believe upstream bz is still down. Got the issue reported here, though: http://bugs.launchpad.net/bugs/881076 Hm, as a workaround probably. I guess it could be added when the test images are done. Unfortunately, when running your image in the cloud it is kind of hard to recover. Even more as you could have tested on an AMD based host. Wonder whether it would be an option to automatically mask the mwait capability off when running in paravirt mode... -Stefan > At least until a good solution is hammered out. > > -- > 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 -- 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
