http://bugzilla.kernel.org/show_bug.cgi?id=14391 --- Comment #11 from Thomas Renninger <trenn@xxxxxxx> 2009-12-11 10:08:20 --- I should have added: CC: stable@xxxxxxxxxx This patch is really trivial and safe and should go there. Be aware that it's not related to suspend, but to all multi core machines that make use of the "managed core" cpufreq implementation (this is when /sys/devices/system/cpu/cpu1/cpufreq is a link to ../cpu0/cpufreq) and when a a _PPC cpufreq BIOS limitation event is thrown to a managed cpu core (in your case the latter always seem to happen on suspend). Dave, can you pick these up, please. This would be: The patch from comment #6: http://bugzilla.kernel.org/attachment.cgi?id=23870 for your next branch and The patch from comment #10: http://bugzilla.kernel.org/show_bug.cgi?id=14391#c10 as a riskless regression fix which should go to mainline/stable kernels asap. Ehh, I cannot change the status, should be code available. -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. -- 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
