weird clock problem

weird clock problem

[Nelis Lamprecht]

Hi,

Over the past few weeks I've been having major problems keeping time on
my machine with kernel 2.6.5. At first I thought it was a problem with
ntpd but as it turns out it's my kernel.

The problem became evident while copying vast amounts of data across to
my machine. While I was copying data to it via scp my random
Xscreensaver kicked in displaying the clock and the first thing I
noticed was that the clock was advancing at a rapid rate. At the same
time I could not type anything as it would just repeat everything I
typed 10 fold. Basically the whole system behaved like it was on
steroids while I was copying to it and by the time I had finished
copying the clock was 2hrs ahead of time. With kernel 2.6.5 ntpd would
work on startup and then die saying no servers could be reached which I
assume was because my clock was so far off.

I have since downgraded to 2.6.3 and now ntpd is keeping time as it
should.

Anybody else come across this behaviour ? I'm running Gentoo on an IBM
ThinkCentre P4 3ghz. I also have APM enabled in both kernels.

Cheers,
Nelis

ps. Please CC me in on your reply as I am not subscribed.

Re: weird clock problem

[john stultz]

On Tue, 2004-05-11 at 06:29, Nelis Lamprecht wrote:
> The problem became evident while copying vast amounts of data across to
> my machine. While I was copying data to it via scp my random
> Xscreensaver kicked in displaying the clock and the first thing I
> noticed was that the clock was advancing at a rapid rate. At the same
> time I could not type anything as it would just repeat everything I
> typed 10 fold. Basically the whole system behaved like it was on
> steroids while I was copying to it and by the time I had finished
> copying the clock was 2hrs ahead of time. With kernel 2.6.5 ntpd would
> work on startup and then die saying no servers could be reached which I
> assume was because my clock was so far off.
> 
> I have since downgraded to 2.6.3 and now ntpd is keeping time as it
> should.

Are you using the ACPI PM timesource? Could you send me your dmesg and
kernel config?

thanks
-john

Re: weird clock problem

[Helge Hafting]

Nelis Lamprecht wrote:

>Hi,
>
>Over the past few weeks I've been having major problems keeping time on
>my machine with kernel 2.6.5. At first I thought it was a problem with
>ntpd but as it turns out it's my kernel.
>
>The problem became evident while copying vast amounts of data across to
>my machine. While I was copying data to it via scp my random
>Xscreensaver kicked in displaying the clock and the first thing I
>noticed was that the clock was advancing at a rapid rate. At the same
>time I could not type anything as it would just repeat everything I
>typed 10 fold. Basically the whole system behaved like it was on
>steroids while I was copying to it and by the time I had finished
>copying the clock was 2hrs ahead of time.
>
Take a look at /proc/interrupts. Is the timer interrupt
shared with something?

Helge Hafting

Re: weird clock problem

[Nelis Lamprecht]

On Wed, 2004-05-12 at 09:04, Helge Hafting wrote:

> >
> Take a look at /proc/interrupts. Is the timer interrupt
> shared with something?
> 

Doesn't look like it.

           CPU0       CPU1
  0:     153901         18    IO-APIC-edge  timer
  1:         89          1    IO-APIC-edge  i8042
  2:          0          0          XT-PIC  cascade
  9:          0          0   IO-APIC-level  acpi
 12:       9271          0    IO-APIC-edge  i8042
 14:       5045          0    IO-APIC-edge  ide0
 15:         43          0    IO-APIC-edge  ide1
 16:       9582          0   IO-APIC-level  uhci_hcd, uhci_hcd, nvidia
 17:          0          0   IO-APIC-level  Intel ICH5
 18:          0          0   IO-APIC-level  uhci_hcd
 19:          0          0   IO-APIC-level  uhci_hcd
 21:        847          0   IO-APIC-level  eth0
 23:          0          0   IO-APIC-level  ehci_hcd
NMI:          0          0
LOC:     153821     153833
ERR:          0
MIS:          0


Regards,
Nelis

RE: weird clock problem

[Piszcz, Justin Michael]

I also have the same problem running Linux 2.6.5 under VMWARE (latest)
for WindowsXP.

If I do not sync every five minutes, the begins to drift a lot!

-----Original Message-----
From: linux-kernel-owner@vger.kernel.org
[mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Nelis Lamprecht
Sent: Tuesday, May 11, 2004 9:30 AM
To: linux-kernel@vger.kernel.org
Subject: weird clock problem

Hi,

Over the past few weeks I've been having major problems keeping time on
my machine with kernel 2.6.5. At first I thought it was a problem with
ntpd but as it turns out it's my kernel.

The problem became evident while copying vast amounts of data across to
my machine. While I was copying data to it via scp my random
Xscreensaver kicked in displaying the clock and the first thing I
noticed was that the clock was advancing at a rapid rate. At the same
time I could not type anything as it would just repeat everything I
typed 10 fold. Basically the whole system behaved like it was on
steroids while I was copying to it and by the time I had finished
copying the clock was 2hrs ahead of time. With kernel 2.6.5 ntpd would
work on startup and then die saying no servers could be reached which I
assume was because my clock was so far off.

I have since downgraded to 2.6.3 and now ntpd is keeping time as it
should.

Anybody else come across this behaviour ? I'm running Gentoo on an IBM
ThinkCentre P4 3ghz. I also have APM enabled in both kernels.

Cheers,
Nelis

ps. Please CC me in on your reply as I am not subscribed.

-
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/