Re: clock suddenly slipping behind

From: Nori Heikkinen (nori_at_sccs.swarthmore.edu)
Date: 08/31/04

  • Next message: Andrew Schulman: "Re: REALTEK driver?"
    Date: Tue, 31 Aug 2004 00:20:47 -0400
    To: Tim Connors <tconnors+linuxdebianuser1093579989@astro.swin.edu.au>, debian-user@lists.debian.org
    
    
    

    on Fri, 27 Aug 2004 11:43:30AM -0400, Nori Heikkinen insinuated:
    > on Fri, 27 Aug 2004 02:21:44PM +1000, Tim Connors insinuated:
    > > Stefan O'Rear <stefanor@cox.net> said on Thu, 26 Aug 2004 20:34:17 -0700:
    > > > On Thu, Aug 26, 2004 at 11:23:07PM -0400, Nori Heikkinen wrote:
    > > > > over the past few days, i've noticed that my system clock gets
    > > > > about ten to fifteen minutes slow over the course of a day.
    > > > > this is really weird! i've been using ntpdate to synchronize
    > > > > it with a timeserver whenever i notice it, and i put it in a
    > > > > once-a-day cron job, but i want my system to ALWAYS be on
    > > > > time. i'm confused as to what's causing this, and how i can
    > > > > fix it. any ideas?
    > > > >
    [...]
    > > I haven't tried to reproduce this, but things to note were the
    > > drift file *seemed* to have normal contents, the adjtime file was
    > > slightly off (but should only affect the hardware timer anyway,
    > > and was probably off because ntp was so confused - you can't
    > > calibrate the hardware clock off a faulty software clock).
    > >
    > > One other very clued in guy on the scary devil monastery also
    > > found this problem a day or two ago. I've been in communication
    > > with him, and it seems these are all related. There is a hard to
    > > trigger bug somewhere, but if you want to track it down, you'll
    > > prbablky need to reinstall old version of ntp and/or adjtimex and
    > > just keep working forwards and backwards until you trigger the bug
    > > again.
    >
    > right now, i've got:
    >
    > ii ntp 4.2.0a-11
    > ii ntp-simple 4.1.0-8
    > ii ntpdate 4.2.0a-11
    > ii adjtimex 1.18-1.1
    >
    > did you get a set of versions that works for you?
    >
    > and if this is a problem with these versions, should i file a bug?
    > hmm, this looks quite relevant:
    > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=265839 (i'm also
    > running kernel 2.4.26-1, like the submitter of this bug).
    >
    > i'll try downgrading adjtimex to 1.13-1, the next lowest version in
    > the cache, and see if i still notice a drift at the end of the day

    so, the drift seems to be entirely gone with the downgrading of
    adjtimex. that bugreport i linked above seems to cover my problem --
    i'm not quite sure (TICK?), but it seems to make sense ("... which
    leads to heavy clock drifts (more than 30 minutes) within a quite
    short time (less than a day) on all my machines. Drifts that not even
    ntpd is able to compensate.").

    if this bug is already filed, i guess my conclusion has to just be to
    keep adjtimex from upgrading until the bug is fixed.

    thanks for your help, all.

    </nori>

    -- 
        .~.      nori @ sccs.swarthmore.edu
        /V\  http://www.sccs.swarthmore.edu/~nori
       // \\          @ maenad.net
      /(   )\       www.maenad.net/jnl
       ^`~'^
      
    ++     Sponsor me as I run my SECOND marathon for AIDS:       ++
    ++ http://www.aidsmarathon.com/participant.asp?runner=DC-2844 ++
    
    

    -- 
    To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
    


  • Next message: Andrew Schulman: "Re: REALTEK driver?"

    Relevant Pages

    • Re: CE 5.0, TIMESVC fails to set clock back to correct time
      ... I will open up a documentation bug so that people know to get their clocks ... Microsoft Corporation ... This posting is provided "AS IS" with no warranties, and confers no rights. ... > Also be aware this may be some sort of protol limitation, as in the clock ...
      (microsoft.public.windowsce.platbuilder)
    • Re: CE 5.0, TIMESVC fails to set clock back to correct time
      ... I have followed your repro steps and see the same bug that you do. ... The real time clocks on systems that we test ... This posting is provided "AS IS" with no warranties, and confers no rights. ... > It seems to depend how far the clock is wrong. ...
      (microsoft.public.windowsce.platbuilder)
    • Re: clock scan (once again)
      ... to *not* do the right thing anymore in that particular case, ... to me seems highly orthogonal to all the restructuring. ... I vaguely remembered some discussion about this change in clock scan, ... bug that I fixed, or an 8.5 bug that I introduced. ...
      (comp.lang.tcl)
    • [PATCH] fix adjtimex() freq return error
      ... Martin Ziegler reported a bug in adjtimex, ... Instead of dividing, we shift, then mult, then shift again, ... I don't think adjtimex() is a terribly hot path, ... uses div_s64to convert back to the external resolution and removes ...
      (Linux-Kernel)
    • [SLE] kde-3.2.1 - kde-3.2.2 and kde-3.2.3 clock applet bug [SOLVED]
      ... In march I reported to the group a bug in clock applet. ... I found the bug, here is the patch. ... copy the patch in a file and after in kdebase-3.2.3 folder ...
      (SuSE)