On Sat, Jan 06, 2007 at 02:24:12PM -0000, Luka Renko wrote: > Marking as confirmed due to many duplicates. > Not sure if the package is appropriate, I would think kernel is more > likely responsible for this.
The kernel could preserve that state across suspend, but it doesn't have to be the kernel's job. user-space should apply the configured policy for CPU hotplug events. This would ensure correct behaviour in all CPU hotplug cases, not just suspend-resume where the kernel hot-unplugs all but one CPU before suspend. (This is maybe only likely to happen with virtual machines, because most desktop hardware isn't physically hotplug safe. And AFAIK Xen prevents cpufreq from working.) -- #define X(x,y) x##y Peter Cordes ; e-mail: X([EMAIL PROTECTED] , des.ca) "The gods confound the man who first found out how to distinguish the hours! Confound him, too, who in this place set up a sundial, to cut and hack my day so wretchedly into small pieces!" -- Plautus, 200 BC -- Dual core sets each core to different cpufreq governor after resume https://launchpad.net/bugs/68191 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
