-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Thursday 2007-12-06 at 14:43 -, Neil Dawkins wrote:
Carlos,
I had a similar problem on one of my 10.3 servers.
I had to reset
/sys/devices/system/clocksource/clocksource0/current_clocksource (in this
case to jiffies).
To list
In message [EMAIL PROTECTED],
Carlos E. R. [EMAIL PROTECTED] writes
The Saturday 2007-12-08 at 18:39 +0100, Anders Johansson wrote:
On Saturday 08 December 2007 17:29:41 Carlos E. R. wrote:
Because of this:
4Marking TSC unstable due to: possible TSC halt in C2.
What is C2?
A power
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Thursday 2007-12-13 at 21:38 -, Roger Hayter wrote:
I don't think it is directly related to your problem, but as an example where
the Linux system clock is not good enough for ntp I have a machine runing
SuSE 9.3 which gains 0.28
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Saturday 2007-12-08 at 01:05 +0100, Carlos E. R. wrote:
Not yet. I think I will compile the kernel tomorrow: it takes about
three hours in this machine.
So, what happened Carlos. Any change?
Not yet, I couldn't... however, I have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Saturday 2007-12-08 at 12:41 +0100, I wrote:
...
Less than half a second of error, with no network! This is indeed
surprising.
It seems that my computer works better with the 'tsc' clocksource than
with the 'acpi_pm' one. Now the problem is
On Saturday 08 December 2007 17:29:41 Carlos E. R. wrote:
The Saturday 2007-12-08 at 12:41 +0100, I wrote:
...
Less than half a second of error, with no network! This is indeed
surprising.
It seems that my computer works better with the 'tsc' clocksource than
with the 'acpi_pm' one.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Saturday 2007-12-08 at 18:39 +0100, Anders Johansson wrote:
On Saturday 08 December 2007 17:29:41 Carlos E. R. wrote:
Because of this:
4Marking TSC unstable due to: possible TSC halt in C2.
What is C2?
A power state. It consumes less
I had to reset
/sys/devices/system/clocksource/clocksource0/current_clocksource (in
this case to jiffies).
To list available sources:
cat /sys/devices/system/clocksource/clocksource0/available_clocksource
Do you know of a link or file with documentation on each type of clock?
Sorry, found
Carlos E. R. wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Thursday 2007-12-06 at 17:26 -0800, Randall R Schulz wrote:
On Thursday 06 December 2007 17:16, Carlos E. R. wrote:
...
Please, remember that the system time does not use the cmos clock and
battery at all. That's a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Friday 2007-12-07 at 08:54 +0100, Frank Fiene wrote:
Sorry for intervening, i haven't read the whole thread!
Do you run Linux in a VM infrastructure like VMware?
No...
- --
Cheers,
Carlos E. R.
-BEGIN PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Friday 2007-12-07 at 08:47 +0100, Hans Witvliet wrote:
On Fri, 2007-12-07 at 02:16 +0100, Carlos E. R. wrote:
You see how the resets increase just the very day I upgraded to 10.3? It
is thus a demonstration that it is a software problem. I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Friday 2007-12-07 at 03:31 -0500, Aaron Kulkis wrote:
In your first post, one of your own logfile excerpts
shows a line where it is syncing to a strata 10 source.
Every line after that shows attempts to re-sync to
a strata 2 source, with very
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Friday 2007-12-07 at 00:15 -0600, David C. Rankin wrote:
I seem to recall that you can adjust the drift of the system clock
within ntp. I don't know if this will cure your problems, but it can't
hurt to check. The file is
Carlos E. R. wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Thursday 2007-12-06 at 12:20 -0500, Aaron Kulkis wrote:
Your logs says that when NTP looses the network connection,
Yes.
it is syncing to the CMOS clock.
No.
You are confusing the system clock with the CMOS clock -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Friday 2007-12-07 at 03:31 -0500, Aaron Kulkis wrote:
Your logs says that when NTP looses the network connection,
Yes.
it is syncing to the CMOS clock.
No.
You are confusing the system clock with the CMOS clock - which is running
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Friday 2007-12-07 at 19:35 -0500, Patrick Shanahan wrote:
The only thing I did was to force the kernel to use the 'tsc' clock
instead of the 'acpi_pm' clocksource it was using:
mine is set to jiffy, but i'm still on 10.1 x86_64
jiffy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Wednesday 2007-12-05 at 00:42 +0100, I wrote:
I'm investigating a problem I'm having with the clock getting very slow,
and I have traced the problem to something new in opensuse 10.3.
Some suggested that the CMOS clock could be running bad.
On Thursday 06 December 2007 08:39:31 pm Carlos E. R. wrote:
The Thursday 2007-12-06 at 20:34 -0600, Rajko M. wrote:
I read a bugzilla at the NTP site, and it appears they think the linux
kernel is broken regarding time adjustment and don't want to hear
anything linux related
Have you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Friday 2007-12-07 at 18:26 -0800, Joseph Loo wrote:
It does sound like your driftfile is messed up.
Which one? There are two.
/var/lib/ntp/drift/ntp.drift? Certainly it is. I did try removing it to
force NTP to recalculate it. No effect.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Friday 2007-12-07 at 14:56 +1100, Basil Chupin wrote:
As the problem started the very same day I upgraded to suse 10.3, that
points to software.
I note that you keep stating that you UPGRADED from 10.2 to 10.3. Does this
mean a NEW
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Friday 2007-12-07 at 16:45 -0600, Rajko M. wrote:
Have you disabled:
[*] Tickless System (Dynamic Ticks)
this is new in 10.3 comparing to 10.2.
Not yet. I think I will compile the kernel tomorrow: it takes about three
hours in this machine.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
* Carlos E. R. [EMAIL PROTECTED] [12-07-07 19:06]:
pending with some logs of this, I'll send it promptly.
The only thing I did was to force the kernel to use the 'tsc' clock
instead of the 'acpi_pm' clocksource it was using:
mine is set to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Thursday 2007-12-06 at 00:18 -0500, Aaron Kulkis wrote:
This is precisely why NTP was invented -- it solves this
problem by obtaining time from calibrated time servers,
and also takes into account network latency. Level 0
Don't you
Aaron Kulkis wrote:
Billie Walsh wrote:
Somewhere in the past I read that computers are wonderful machines.
Capable of great things. BUT, they are horrible clocks.
The way it was explained was that when system use was high and resources
were strained the clock was the last thing to get
Carlos E. R. wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Thursday 2007-12-06 at 00:18 -0500, Aaron Kulkis wrote:
This is precisely why NTP was invented -- it solves this
problem by obtaining time from calibrated time servers,
and also takes into account network latency. Level
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Friday 2007-12-07 at 00:05 +1100, Basil Chupin wrote:
Carlos,
I haven't been paying too much attention to what you have written re the
problem, what result do you get when you try setting the time manually, as
root, from the command line?
Carlos E. R. wrote:
The Friday 2007-12-07 at 00:05 +1100, Basil Chupin wrote:
Carlos,
I haven't been paying too much attention to what you have written re
the problem, what result do you get when you try setting the time
manually, as root, from the command line? You know, the old
ntpdate
Neil Dawkins wrote:
Carlos E. R. wrote:
The Friday 2007-12-07 at 00:05 +1100, Basil Chupin wrote:
Carlos,
I haven't been paying too much attention to what you have written re
the problem, what result do you get when you try setting the time
manually, as root, from the command line? You
On December 6, 2007 05:54:39 am Carlos E. R. wrote:
The Friday 2007-12-07 at 00:05 +1100, Basil Chupin wrote:
Carlos,
I haven't been paying too much attention to what you have written re the
problem, what result do you get when you try setting the time manually,
as root, from the
Carlos E. R. wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Friday 2007-12-07 at 00:05 +1100, Basil Chupin wrote:
Carlos,
I haven't been paying too much attention to what you have written re
the problem, what result do you get when you try setting the time
manually, as root,
Robert Smits wrote:
On December 6, 2007 05:54:39 am Carlos E. R. wrote:
The Friday 2007-12-07 at 00:05 +1100, Basil Chupin wrote:
Carlos,
I haven't been paying too much attention to what you have written re the
problem, what result do you get when you try setting the time manually,
as root,
Carlos E. R. wrote:
The problem is that NTP can't keep the system clock disciplined, it
strays off as soon as NTP looses the network peers, and not a second
or two, but several minutes.
It seems a kernel problem, not an NTP problem.
Just out of curiosity, are you running the stock suse
Carlos E. R. wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Thursday 2007-12-06 at 00:18 -0500, Aaron Kulkis wrote:
This is precisely why NTP was invented -- it solves this
problem by obtaining time from calibrated time servers,
and also takes into account network latency. Level
Neil Dawkins wrote:
Carlos E. R. wrote:
The Friday 2007-12-07 at 00:05 +1100, Basil Chupin wrote:
Carlos,
I haven't been paying too much attention to what you have written re
the problem, what result do you get when you try setting the time
manually, as root, from the command line? You
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Thursday 2007-12-06 at 17:26 -0800, Randall R Schulz wrote:
On Thursday 06 December 2007 17:16, Carlos E. R. wrote:
...
Please, remember that the system time does not use the cmos clock and
battery at all. That's a different clock
On Thursday 06 December 2007 17:16, Carlos E. R. wrote:
...
Please, remember that the system time does not use the cmos clock and
battery at all. That's a different clock altogether. Plus, the cmos
clock is running fine, I'm checking it at the moment.
... at all ...? I don't think this is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Thursday 2007-12-06 at 09:52 -0800, Sloan wrote:
It seems a kernel problem, not an NTP problem.
Just out of curiosity, are you running the stock suse kernel, or did you
install something newer. I'd never had any problem with ntp on the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Thursday 2007-12-06 at 14:43 -, Neil Dawkins wrote:
Carlos,
I had a similar problem on one of my 10.3 servers.
I had to reset
/sys/devices/system/clocksource/clocksource0/current_clocksource (in this
case to jiffies).
To list
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Thursday 2007-12-06 at 09:02 -0800, Robert Smits wrote:
It seems a kernel problem, not an NTP problem.
Actually, it looks way more like a hardware problem than a software problem.
Normally I can run any of my systems for more than a month
Aaron Kulkis wrote:
Carlos E. R. wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Thursday 2007-12-06 at 00:18 -0500, Aaron Kulkis wrote:
This is precisely why NTP was invented -- it solves this
problem by obtaining time from calibrated time servers,
and also takes into account
On Thursday 06 December 2007 17:38, Carlos E. R. wrote:
The Thursday 2007-12-06 at 17:26 -0800, Randall R Schulz wrote:
On Thursday 06 December 2007 17:16, Carlos E. R. wrote:
...
Please, remember that the system time does not use the cmos clock
and battery at all. ...
... at all
On Fri, 2007-12-07 at 02:30 +0100, Carlos E. R. wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Thursday 2007-12-06 at 12:11 -0500, Aaron Kulkis wrote:
Don't you understand that NTP can not adjust my system clock and quits?
Yes I do.
I was explaining NTP it to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Thursday 2007-12-06 at 12:28 -0500, Aaron Kulkis wrote:
Changing the CMOS battery would be simpler, and costs less
than lunch in a restaurant.
The system time is not affected by the CMOS battery at all.
- --
Cheers,
Carlos E. R.
On Thursday 06 December 2007 07:22:32 pm Carlos E. R. wrote:
I have tried several frequency settings, from 250 (default) to 1000. No
appreciable difference regarding this problem.
I read a bugzilla at the NTP site, and it appears they think the linux
kernel is broken regarding time
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Thursday 2007-12-06 at 12:11 -0500, Aaron Kulkis wrote:
Don't you understand that NTP can not adjust my system clock and quits?
Yes I do.
I was explaining NTP it to Billie Walsh, who didn't seem
to understand that NTP is a method of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Thursday 2007-12-06 at 17:49 -0800, Joseph Loo wrote:
It does sound like your driftfile is messed up.
Which one? There are two.
/var/lib/ntp/drift/ntp.drift? Certainly it is. I did try removing it to
force NTP to recalculate it. No
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Thursday 2007-12-06 at 17:47 -0800, Joseph Loo wrote:
I believe that the CMOS clock is updated when you shutdown. There is a
specific routine that synchronize the cmos clock.
Yes, that is correct.
Have a look here - it is old, but mostly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Thursday 2007-12-06 at 12:20 -0500, Aaron Kulkis wrote:
Your logs says that when NTP looses the network connection,
Yes.
it is syncing to the CMOS clock.
No.
You are confusing the system clock with the CMOS clock - which is running
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Thursday 2007-12-06 at 17:58 -0800, Randall R Schulz wrote:
Not really. I have been using this same machine without permanent
network, and thus, no NTP, for years, and the clock drift was about a
second or two per day.
Then you have the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Thursday 2007-12-06 at 20:34 -0600, Rajko M. wrote:
I read a bugzilla at the NTP site, and it appears they think the linux
kernel is broken regarding time adjustment and don't want to hear
anything linux related
Have you disabled:
[*]
On Fri, 2007-12-07 at 02:38 +0100, Carlos E. R. wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Thursday 2007-12-06 at 17:26 -0800, Randall R Schulz wrote:
On Thursday 06 December 2007 17:16, Carlos E. R. wrote:
...
Please, remember that the system time does not use
Carlos E. R. wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Thursday 2007-12-06 at 17:58 -0800, Randall R Schulz wrote:
Not really. I have been using this same machine without permanent
network, and thus, no NTP, for years, and the clock drift was about a
second or two per day.
Carlos E. R. wrote:
The Thursday 2007-12-06 at 09:02 -0800, Robert Smits wrote:
It seems a kernel problem, not an NTP problem.
Actually, it looks way more like a hardware problem than a software
problem.
Normally I can run any of my systems for more than a month without
being more
On Fri, 2007-12-07 at 02:16 +0100, Carlos E. R. wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Thursday 2007-12-06 at 09:02 -0800, Robert Smits wrote:
It seems a kernel problem, not an NTP problem.
Actually, it looks way more like a hardware problem than a software
On Freitag 07 Dezember 2007, Carlos E. R. wrote:
[...]
I have tried several frequency settings, from 250 (default) to 1000.
No appreciable difference regarding this problem.
I read a bugzilla at the NTP site, and it appears they think the
linux kernel is broken regarding time adjustment
On Wed, 2007-12-05 at 22:48 +0100, Theo v. Werkhoven wrote:
Tue, 04 Dec 2007, by [EMAIL PROTECTED]:
Somewhere in the past I read that computers are wonderful machines.
Capable of great things. BUT, they are horrible clocks.
The way it was explained was that when system use was high and
Tue, 04 Dec 2007, by [EMAIL PROTECTED]:
Somewhere in the past I read that computers are wonderful machines.
Capable of great things. BUT, they are horrible clocks.
The way it was explained was that when system use was high and resources
were strained the clock was the last thing to get
Tue, 04 Dec 2007, by [EMAIL PROTECTED]:
Carlos E. R. wrote:
The Tuesday 2007-12-04 at 17:41 -0800, Joseph Loo wrote:
On Tue, 2007-12-04 at 20:24 -0500, James Knott wrote:
grep time reset /var/log/ntp | less
I get 24 Oct 19:41:38 ntpd[3347]: time reset -0.130426 s
29
On Wednesday 05 December 2007 06:03:54 pm Carlos E. R. wrote:
The Wednesday 2007-12-05 at 22:48 +0100, Theo v. Werkhoven wrote:
don't know where you got that from, but ever since the IBM AT, PC's have
had a hardware clock on the mainboard, independent of the OS or user
programs.
The only
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Wednesday 2007-12-05 at 22:48 +0100, Theo v. Werkhoven wrote:
don't know where you got that from, but ever since the IBM AT, PC's have
had a hardware clock on the mainboard, independent of the OS or user
programs.
The only thing that can make
Rajko M. wrote:
On Wednesday 05 December 2007 06:03:54 pm Carlos E. R. wrote:
The Wednesday 2007-12-05 at 22:48 +0100, Theo v. Werkhoven wrote:
don't know where you got that from, but ever since the IBM AT, PC's have
had a hardware clock on the mainboard, independent of the OS or
On Wednesday 05 December 2007 09:52:43 pm Carlos E. R. wrote:
The thing is, I don't know how these settings were in 10.2 or earlier.
It was not
[*] Tickless System (Dynamic Ticks)
That means disabling this, and enabling some of fixed will bring in the same
state as 10.2.
That doesn't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I'm investigating a problem I'm having with the clock getting very slow,
and I have traced the problem to something new in opensuse 10.3.
I wonder if any body has the same problem - the check is simple, run this
grep command:
grep time
Carlos E. R. wrote:
I'm investigating a problem I'm having with the clock getting very slow,
and I have traced the problem to something new in opensuse 10.3.
I believe there must be a kernel problem or ntp problem in 10.3.
Excellent work, Carlos, someone on PCLinux told me of a similar
problem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Wednesday 2007-12-05 at 01:05 +0100, Philippe Landau wrote:
Carlos E. R. wrote:
I'm investigating a problem I'm having with the clock getting very slow,
and I have traced the problem to something new in opensuse 10.3.
I believe there must be
Carlos E. R. wrote:
Hi,
I'm investigating a problem I'm having with the clock getting very
slow, and I have traced the problem to something new in opensuse 10.3.
I wonder if any body has the same problem - the check is simple, run
this grep command:
grep time reset /var/log/ntp | less
On Tue, 2007-12-04 at 20:24 -0500, James Knott wrote:
Carlos E. R. wrote:
Hi,
I'm investigating a problem I'm having with the clock getting very
slow, and I have traced the problem to something new in opensuse 10.3.
I wonder if any body has the same problem - the check is simple,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Tuesday 2007-12-04 at 17:41 -0800, Joseph Loo wrote:
On Tue, 2007-12-04 at 20:24 -0500, James Knott wrote:
grep time reset /var/log/ntp | less
I get 24 Oct 19:41:38 ntpd[3347]: time reset -0.130426 s
29 Oct 18:20:20 ntpd[3433]: time
Somewhere in the past I read that computers are wonderful machines.
Capable of great things. BUT, they are horrible clocks.
The way it was explained was that when system use was high and resources
were strained the clock was the last thing to get updated. Thus, it
looses time. I'm sure it isn't
Carlos E. R. wrote:
The Tuesday 2007-12-04 at 17:41 -0800, Joseph Loo wrote:
On Tue, 2007-12-04 at 20:24 -0500, James Knott wrote:
grep time reset /var/log/ntp | less
I get 24 Oct 19:41:38 ntpd[3347]: time reset -0.130426 s
29 Oct 18:20:20 ntpd[3433]: time reset -0.145680 s
8 Nov
70 matches
Mail list logo
