-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Somebody in the thread at some point said: | Hi, | | I've noticed that my FR clock runs slower than normal clock. I'm using | andy-tracking 4ff379a06a70e179 | | Since it happens no matter if device is powered up or powered down, I'm | assuming (maybe wrongly) it's RTC related. | | It's _not_ caused by suspend/resume. | | Log from framework illustrates it pretty well. | | cat /var/log/frameworkd.log | grep "adjusting clock" | 2009.01.16 22:28:47 otimed INFO adjusting clock by 766.051786 seconds | 2009.01.16 22:34:51 otimed INFO adjusting clock by 777.347250 seconds | 2009.01.17 16:42:25 otimed INFO adjusting clock by 1093.032441 seconds
Is it possible it fails to set the hw / rtc clock? It's suspicious the adjustment it wants to make is always going up monotonically and jumps according to elapsed time, it's as if it never manages to adjust it. - -Andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkl0zjsACgkQOjLpvpq7dMoCVwCfe/c8FHbKahUd8E1/qXA5IRca GTsAn2Z4H113kMVi1zE89AQv/VDZ4MMx =f2sR -----END PGP SIGNATURE-----
