Hi,
At 18:21 06/04/2005, Jon Noack wrote:
[...] I only got resets on the SMP/ULE machine. Perhaps SMP or ULE make
the issue worse?
I'm seeing it on both SMP and UP boxes on the same LAN, not running ULE.
--
Bob Bishop +44 (0)118 940 1243
[EMAIL PROTECTED] fax +44 (0
On 04/01/05 14:51, Vivek Khera wrote:
On Apr 1, 2005, at 12:56 PM, Bob Bishop wrote:
At 18:42 01/04/2005, Roland Smith wrote:
On my amd64 box I also get the mode flipping, but I don't get resets.
Hmm. I am getting resets on my amd64.
On my dual opteron, I get flipping perhaps a handful of times per
On Apr 6, 2005, at 07:04, Bob Bishop wrote:
I'm currently runnning a 5.3 with the ntpd from 5.2.1 (ie version
4.1.1 not 4.2.0); looks good so far, I'll report back after a sensible
interval.
You may also want to poke your head into comp.protocols.time.ntp with
this issue. Some of the designers a
Hi,
At 11:45 06/04/2005, Andriy Gapon wrote:
I can not explain it, but I've suddenly got a gut feeling that the
subject discussed might be a result of revision 1.53 of
sys/kern/kern_ntptime.c
Nope. Tried that (backed it out to 1.52), no improvement.
I'm currently runnning a 5.3 with the ntpd from 5
on 06.04.2005 11:13 Andriy Gapon said the following:
> I am using the default value of maxpoll, no overrides.
> So, IMO this leaves one possibility: mtemp > 2048, i.e. hardupdate() was
> not called for longer than this time i.e. either ntp_adjtime() was not
> called or it was called without MOD_OFF
on 05.04.2005 22:32 Peter Jeremy said the following:
> Note that this code doesn't exist in 5.3. It was introduced sometime
> between 5.3 and 5.4. In any case, looking at the associated comments,
> this only affects the FLL/PLL loop gain.
Yes, I see that I looked in a wrong place.
> The FLL/PLL
On Tue, 2005-Apr-05 15:01:07 +0300, Andriy Gapon wrote:
>on 01.04.2005 20:40 Bob Bishop said the following:
>>
>> Unlikely I think. As I said, I've got several machines on the same LAN:
>> the 5.3's misbehave; the others don't.
>
>#define CLOCK_ALLAN 1500.
>...
>doubleallan_xpt =
on 01.04.2005 20:40 Bob Bishop said the following:
>
> Unlikely I think. As I said, I've got several machines on the same LAN:
> the 5.3's misbehave; the others don't.
#define CLOCK_ALLAN 1500.
...
doubleallan_xpt = CLOCK_ALLAN;
...
if (ULOGTOD(sys_poll) > allan_xpt / 2) {
...
On Apr 1, 2005, at 12:56 PM, Bob Bishop wrote:
At 18:42 01/04/2005, Roland Smith wrote:
On my amd64 box I also get the mode flipping, but I don't get resets.
Hmm. I am getting resets on my amd64.
On my dual opteron, I get flipping perhaps a handful of times per day
(5.4-PRE/amd64 from march 22).
On Fri, 2005-Apr-01 19:38:41 +0300, Andriy Gapon wrote:
>I can second that. I have never seen anything like this with 5.2.1 as
>soon as I upgraded to 5.3 I started seeing messages like these:
...
>Mar 29 22:15:40 oddity ntpd[400]: time reset -0.288522 s
>Mar 29 22:15:40 oddity ntpd[400]: kernel tim
Hi,
At 18:42 01/04/2005, Roland Smith wrote:
On my amd64 box I also get the mode flipping, but I don't get resets.
Hmm. I am getting resets on my amd64.
--
Bob Bishop +44 (0)118 940 1243
[EMAIL PROTECTED] fax +44 (0)118 940 1295
___
On Fri, Apr 01, 2005 at 02:24:50PM +0100, Bob Bishop wrote:
> >>Any suggestions as to why this is happening? (And how I can stop
> >>it regularly flipping)
> >
> >I don't think this is really an issue. [etc]
>
> I think this is an issue:
>
> - As stated, machines running 4.x don't seem to do it
Hi,
At 17:38 01/04/2005, Andriy Gapon wrote:
[...]
I suppose that it might be possible that the root cause is in my local
network conditions, [etc]
Unlikely I think. As I said, I've got several machines on the same LAN: the
5.3's misbehave; the others don't.
--
Bob Bishop +44 (0)
on 01.04.2005 16:24 Bob Bishop said the following:
> I think this is an issue:
>
> - As stated, machines running 4.x don't seem to do it
> - In addition to the mode schizophrenia, undex 5.3 I'm also seeing
> resets of several seconds which don't happen on identical hardware
> running 4.11 in the s
Hi,
At 14:04 01/04/2005, David Magda wrote:
On Apr 1, 2005, at 05:45, Peter Jeremy wrote:
Any suggestions as to why this is happening? (And how I can stop
it regularly flipping)
I don't think this is really an issue. [etc]
I think this is an issue:
- As stated, machines running 4.x don't seem to d
On Apr 1, 2005, at 05:45, Peter Jeremy wrote:
Any suggestions as to why this is happening? (And how I can stop
it regularly flipping)
I don't think this is really an issue. It may be annoying to see it in
the logs, but NTPv4 uses each algorithm when it's appropriate to get
the most accurate time
My 5.x machines are regularly reporting that the kernel is flipping
between FLL and PLL mode (as shown by STA_MODE in syslog messages).
This isn't occuring on my 4.x machines (they typically report 2040
then 2041 and stay indefinitely in that mode).
Any suggestions as to why this is happening? (A
17 matches
Mail list logo
