All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sid Boyce <sboyce@blueyonder.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: later kernels vs ntpd
Date: Mon, 19 Sep 2005 22:40:59 +0100	[thread overview]
Message-ID: <432F306B.40503@blueyonder.co.uk> (raw)

Gene Heskett wrote:
 > Someone suggested that I needed the ipv6 stuff, so I built a 2.6.13.1
 > with all that turned on, but an overnight run of it also failed to
 > synch, so I'm back on 2.6.13-rc5, which works well.
 >
 > But this is preventing me from playing the coal mine canary. Does
 > anyone else have a suggestion?

Right up to 2.6.13-rc6-git12 I've used 
linux-2.6.13-rc6_timeofday-all.patch with no drift at all. With 
unpatched kernels (won't apply) up to 2.6.14-rc1-git5 on SuSE 9.3, I'm 
seeing -3 secs drift since reboot 1 hour ago, I think that's the max 
I've seen over several hours, I have a heat/hardware problem that causes 
a solid lockup at random times.
On the other box with the same hardware and Mandriva LE2005, no drift.
bumble:/root # ptktime&
[1] 27567
bumble:/root # localhost                       0 Mon Sep 19 22:35:58 2005
128.118.25.3                    0 Mon Sep 19 22:35:58 2005

bumble:/root # uptime
  22:36:15 up 22:35,  3 users,  load average: 0.00, 0.00, 0.00
bumble:/root # uname -r
2.6.14-rc1-git4

Regards
Sid.
-- 
Sid Boyce ... Hamradio License G3VBV, licensed Private Pilot
Retired IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support 
Specialist
Microsoft Windows Free Zone - Linux used for all Computing Tasks

             reply	other threads:[~2005-09-19 21:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-19 21:40 Sid Boyce [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-09-18 14:46 later kernels vs ntpd Gene Heskett
2005-09-18 14:59 ` Gene Heskett
2005-09-19 13:00   ` Gene Heskett

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=432F306B.40503@blueyonder.co.uk \
    --to=sboyce@blueyonder.co.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.