https://bugzilla.kernel.org/show_bug.cgi?id=55411 --- Comment #8 from Viresh Kumar <viresh.kumar@xxxxxxxxxx> 2013-03-19 06:16:53 --- (In reply to comment #0) > Abridged (perms/dates omitted) fresh-boot (good) > ls -dl /sys/devices/system/cpu/cpu?/cpufreq : > > /sys/devices/system/cpu/cpu0/cpufreq/ > /sys/devices/system/cpu/cpu1/cpufreq -> ../cpu0/cpufreq/ > /sys/devices/system/cpu/cpu2/cpufreq/ > /sys/devices/system/cpu/cpu3/cpufreq -> ../cpu2/cpufreq/ > /sys/devices/system/cpu/cpu4/cpufreq/ > /sys/devices/system/cpu/cpu5/cpufreq -> ../cpu4/cpufreq/ > > After a s2ram/resume cycle (now bad): > > /sys/devices/system/cpu/cpu0/cpufreq/ > /sys/devices/system/cpu/cpu1/cpufreq -> ../cpu0/cpufreq/ > /sys/devices/system/cpu/cpu3/cpufreq/ > /sys/devices/system/cpu/cpu5/cpufreq/ Can you try this rather than s2r: for i in 1 2 3 4 5; do echo 0 > /sys/devices/system/cpu/cpu$i/online ; done for i in 1 2 3 4 5; do echo 1 > /sys/devices/system/cpu/cpu$i/online ; done and check the status if things are still corrupted for you? I am working on a 5 cpu system grouped as 0-1 and 2-3-4. Above doesn't corrupt anything for me Atleast. And my system doesn't have S2R support for now. -- Configure bugmail: https://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
