On Mon, Mar 21, 2011 at 9:33 AM, wu zhangjin <[email protected]> wrote: > On Mon, Mar 21, 2011 at 1:13 AM, Roman Mamedov <[email protected]> wrote: >> On Sun, 20 Mar 2011 08:59:34 -0700 (PDT) >> Roman Mamedov <[email protected]> wrote: >> >>> 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). > > MFGPT did have broken system clock, that's why we have disabled it. > and of course, If don't consider cpufreq, MFGPT with periodic mode > basically works. > >> >> It locked up with MFGPT too (but after about 5 hours of operation), so I >> guess >> it's something else. > > Seems lock-up have been reported by several guys, so, It is really > time for us to fix it asap. > > Can you disable cpufreq and try it again?
If it doesn't help, could you please try to revert the following two patches: MIPS: Add current_cpu_prid() to optimize the code generation MIPS: Use current_cpu_type() instead of c->cputype Regards, > > BTW, what is the lock-up you encountered? can you wake it up by key > press? If it suspends automatically with the setting of > gnome-power-manager, then, keyboard should be able to wake the system > up. > > Regards, > Wu Zhangjin > >> >> -- >> With respect, >> Roman >> > -- You received this message because you are subscribed to the Google Groups "loongson-dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/loongson-dev?hl=en.
