[ltp] Re: System clock wrong on resume from ACPI suspend in recent FC3 update

[Ruben Jenster]

--nextPart2766233.m2GPRVxOhY
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Am Monday, 14. February 2005 13:22 schrieb Philip Balister:
> I have exactly the same problem on a DELL 600m. It was driving me wacky
> until I figured out why the clock was always wrong.
>
> I also have the impression the amount of time shift is proportional to
> the amount of time the computer is asleep.
>
> Philip
>
> On Fri, 2005-01-21 at 12:22 -0500, Eric Benson wrote:
> > On a Thinkpad T41p running Fedora Core 3 kept up-to-date since November.
> > Recently, in the past two or three weeks, the clock has been incorrect
> > every time I resume from ACPI suspend. Before that it was always correct
> > when it woke up. Now the clock is always fast when it wakes up. It
> > appears to be proportional to how long it has been sleeping, as if the
> > clock were running consistently extremely fast while asleep, but I
> > haven't run any tests to see if it is reproducible. I've been fixing it
> > by restarting ntpd. I'm currently running kernel 2.6.10-1.741, but I've
> > had all of the kernel updates since FC3 came out. I can't say for sure
> > that the problem started with a kernel update, but it may have coincided
> > with the first 2.6.10 kernel.
> >
> > Is this a known problem? Is there a fix?

Try the newest acpi patch from=20
http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches/release
Since I use the 2.6.9 Kernel with the newest acpi patch on my T41p the time=
=20
drift problem is gone.

Regards=20

Ruben

--nextPart2766233.m2GPRVxOhY
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQBCER750gsecz4c07sRAn5NAJ9ytWX1HsdB5gwOre5NtuzQSe1CcgCgpsSW
ygVn7H3GYuod0dyJiQ0cHEY=
=sgzv
-----END PGP SIGNATURE-----

--nextPart2766233.m2GPRVxOhY--