public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Frank <mhf@linuxmail.org>
To: Bill Anderson <banderson@hp.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: system (not HW) clock advancing really fast
Date: Mon, 16 Feb 2004 14:24:49 +0800	[thread overview]
Message-ID: <200402161424.49242.mhf@linuxmail.org> (raw)
In-Reply-To: <1076910368.25980.12.camel@perseus>

I had this somtetimes when using ntpd doing step time update
resulting in silly values in /etc/adjtime . 

# mv /etc/adjtime /tmp 
# hwclock --systohc

and see if it goes away.

Regards
Michael

On Monday 16 February 2004 13:46, Bill Anderson wrote:
> Kernel version: 
> 	2.4.24-xfs
> 	We've apaprently had this problem for a while
> 
> Ok, I've got an HP LPr machine, dual 700MHz intel machine that has it's
> system clock gaining seconds very quickly. This, I am told, has been
> happening for several kernels.
> 
> At first, others on the team insisted it was the hardware clock at
> fault, as rebooting the system gives the appearance of fixing it.
> However, the system is currently having this issue, and the HW clock is
> actually keeping accurate time, as I expected.
> 
> The time gain is no consistent. It can gain 3 seconds in one, or 12 in
> 11, but it always runs fast. This time speedup is to much for ntp to
> keep up with. If I sync from hwclock or ntpdate every second, I'm
> correcting about 1-3 seconds each time. This is a mail server, so I am
> sure you can appreciate the need for accurate timestamps. ;)
> 
> I've seen many messages in the archives about *losing* time, but only a
> few about gaining it. Personally, I am opposed to the "just reboot it"
> mentality; one reason I run Linux.
> 
> Given that we are talking about system clock, not HW, and that this
> happens with or w/o ntpd/ntpdate, I am suspecting something in the
> kernel. Also, this thread leads me there too:
> http://marc.theaimsgroup.com/?l=linux-kernel&m=105465355622844&w=2
> 
> 
> Am I off base here? I can probably keep the hwclock sync method running
> for a day or so before I'm forced to reboot it, so if there is anything
> you need to know or want me to try while it is in this state, let me
> know.
> 
> This address is not subscribed, so please cc me on responses.
> 
> Thanks,
> 
> Bill
> 
> 
> 
> 
> -- 
> Bill Anderson <banderson@hp.com>
> Red Hat Certified Engineer
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 
> 


  reply	other threads:[~2004-02-16  6:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-16  5:46 system (not HW) clock advancing really fast Bill Anderson
2004-02-16  6:24 ` Michael Frank [this message]
2004-02-16  7:26   ` Bill Anderson
2004-02-16  7:45     ` Michael Frank
2004-02-16  7:48       ` Bill Anderson
2004-02-16  8:41         ` Michael Frank
2004-02-16  8:50           ` Michael Frank

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=200402161424.49242.mhf@linuxmail.org \
    --to=mhf@linuxmail.org \
    --cc=banderson@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox