mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vladimir Lazarenko <vlad@lazarenko.net>
To: john stultz <johnstul@us.ibm.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.14-rc5 (i386) + TSC, how to disable? time drift
Date: Thu, 27 Oct 2005 04:33:55 +0200	[thread overview]
Message-ID: <43603C93.1070109@lazarenko.net> (raw)
In-Reply-To: <1130377451.27168.386.camel@cog.beaverton.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]

> On Thu, 2005-10-27 at 03:13 +0200, Vladimir Lazarenko wrote:
> 
>>Hello,
>>
>>To continue on my struggle with Dual-core - another interesting issue 
>>popped up: time drift.
>>
>>SMP is enabled, TSC is enabled.
> 
> 
> It looks like you have ACPI PM and HPET enabled in the kernel, so it
> appears your system does not support alternative clocksources. 
> 
> You can check to see if a updated BIOS that makes ACPI PM or HPET
> available to the OS has been released, or request one from your hardware
> vendor.
> 
> You might want to try idle=poll as well.

Thank you john. So far, idle=poll seemed to help, partially.
The time doesn't go backwards for now, it only occasionally skips a 
second, every 2-3 minutes. Is that normal? Not that I have been watching 
seconds very closely at any previous moment, so I can't say if it has 
ever happened before.

And I dont' know if this question can be addressed to you, but can you 
say something about those /proc/interrupts? Why don't I see any 
interrupts except LOC being handled by 2nd CPU core?

Thanks in advance!

Vladimir

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3412 bytes --]

      reply	other threads:[~2005-10-27  2:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-27  1:13 Vladimir Lazarenko
2005-10-27  1:44 ` john stultz
2005-10-27  2:33   ` Vladimir Lazarenko [this message]

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=43603C93.1070109@lazarenko.net \
    --to=vlad@lazarenko.net \
    --cc=johnstul@us.ibm.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

all inboxes | Powered by JetHome®