On Tue, Apr 9, 2013 at 6:51 PM, Viresh Kumar <viresh.kumar@xxxxxxxxxx> wrote: > On 9 April 2013 21:38, Sedat Dilek <sedat.dilek@xxxxxxxxx> wrote: >> With x=3 the system gets in an unuseable state. >> >> root# echo 0 > /sys/devices/system/cpu/cpu3/online >> >> I could not write my reply and had to do a hard/cold reboot. >> The dmesg log I saw looked similiar to my digicam-shot. > > Few things i need from you. First is output of cpufreq-info. Then > all the steps you did to reproduce above? Removed any other cpus? > > I am not able to find next-20130326 tag in my repo, only have 23 and 28. > Can you debug it a bit to find exact line of code causing this issue using > objdump? > > HINT: Documentation/BUG-HUNTING.. > next-20130326 see... [1] http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/tag/?id=next-20130326 objdump of file? > Give me line numbers of both of these functions: __cpufreq_governor() and > __cpufreq_remove_dev(). I must checkout by myself and jump on next-20130326. Unfortunately, I have it installed but have no binaries and deleted the branch from my local GIT branch. Still on the fs/pipe issue from vfs-next :-). I guess I have a working follow-up patch, still compiling. - Sedat - -- 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
