On Tue, Jun 16, 2009 at 11:32, Nils Faerber<[email protected]> wrote: > Timo Juhani Lindfors schrieb: >> Nils Faerber <[email protected]> writes: >>> Is this "sporadic", i.e. does this error occur sometimes and after the >>> error it works again? >> >> Yes. >> >>> It could also be that if there is traffic on the serial line in the very >>> same moment when the frequency change occurs the UART looses its clock >> >> I thought I set the clock permanently to 100 MHz when I ran >> >> sudo sh -c "echo powersave > >> /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor" >> >> What kind of frequency changes are you talking about? > > Oh, OK, I had the impression that you were using something like the > ondemand cpufreq governor. > If the CPU clock sticks to the powersave governor's 100MHz then my > theory is void.
I think this issue isn't related to cpufreq - I have that on standard andy-tracking kernel. And for me it happens always - I'm unable to use GPS at all...
