Hello! Has anyone seen Yeeloong lock-up when using cpufreq on recent kernels?
I tried kernels 2.6.37 and 2.6.38 from both anheng.com.cn and linux- libre, and on those kernels enabling cpufreq governors ondemand or conservative makes my Yeeloong lock up pretty quickly (in 5-10 minutes, though sometimes it works for longer). Interestingly, there are no lockups whatsoever when I run the same kernels on Lemote Fuloong. But the Yeeloong is stable only when I select the performance governor, or switch to an older kernel (tried 2.6.32.32 so far). I have investigated a bit, and found that there indeed has been an issue with cpufreq and clocksources, which was at first solved by using CS5536 MFGPT, then by a patch implementing an R4K clocksource: http://dev.lemote.com/cgit/linux-loongson-community.git/commit/?id=76a17a7dd11a7fc79168bc76d36905b9160a93ee&h=linux-2.6.37-stable&=switch https://groups.google.com/group/loongson-dev/browse_thread/thread/339897d8b8e1472b/3fecd45468d02887 So I have now built my own 2.6.38 kernel with the MFGPT clocksource, and it seems to be stable and not locking up. MFGPT was blamed to slow down system clock by 12 seconds in an hour, but I currently do not observe this (running ntpdate every couple of hours does not lead to sizeable adjustments). -- You received this message because you are subscribed to the Google Groups "loongson-dev" group. To post to this group, send email to loongson-dev@googlegroups.com. To unsubscribe from this group, send email to loongson-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/loongson-dev?hl=en.
