archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <>
To: "Michèl Alexandre Salim" <>,
Subject: Re: Clock drift on Transmeta Crusoe
Date: Mon, 11 Jun 2001 22:33:57 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>
In-Reply-To: =?iso-8859-1?Q?=3C20010611113604=2E4073=2Eqmail=40web3504=2Email=2Eyahoo?= =?iso-8859-1?Q?=2Ecom=3E=3B_from_Mich=E8l_Alexandre_Salim_on_Mon=2C_Jun_?= =?iso-8859-1?Q?11=2C_2001_at_12:36:04PM_+0100?=


> Searching through the mailing list I could not find a
> reference to this problem, hence this post.
> Having ran various kernel and distribution
> combinations (SGI's 2.4.2-xfs bundled with their Red
> Hat installer, 2.4-xfs-1.0 and 2.4 CVS trees, Linux
> Mandrake with default kernel 2.4.3, and lastly
> 2.4.5-ac9), compiled for generic i386 and/or Transmeta
> Crusoe with APM off or on, one thing sticks out : a
> clock drift of a few minutes per day.
> This problem might not be noticeable for most users
> since notebooks are not normally left running that
> long, but it is rather serious. I can choose not to
> sync the software and hardware clock on shutdown and
> re-read the hardware clock every hour or so but it is
> rather kludgy.
> Any suggestions and/or user experiences more than
> welcome.

Let me guess: vesafb?

If problem goes away when you stop using framebuffer (i.e. go X), then
it is known. 

You are lucky. My machine is able to loose 2 minutes from every 3

try time cat /etc/termcap, and check it against stopwatch.
I'm "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at

  reply	other threads:[~2001-06-12  8:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-11 11:36 Michèl Alexandre Salim
2001-06-11 20:33 ` Pavel Machek [this message]
2001-06-12 16:32   ` Alan Cox
2001-06-12 21:00   ` Michèl Alexandre Salim
2001-06-12 22:10     ` Pavel Machek
2001-06-12 10:26 ` Jonathan Morton
2001-06-12 20:58   ` Michèl Alexandre Salim

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \
    --subject='Re: Clock drift on Transmeta Crusoe' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).