On Wed, 08 Dec 2010 09:59:26 +1030
Tim wrote:
> I don't think the original poster said which clock was skewing.
There are indeed a gazillion or so clock options you can
specify on the kernel command line. Perhaps making it
use a different clock source would work better. (The kernel
may believe it
On Tue, 2010-12-07 at 15:21 -0800, Konstantin Svist wrote:
> I agree it wouldn't hurt to check, but AFAIK, Linux only reads the
> CMOS clock on startup and until shutdown keeps track of time using CPU
> cycles -- which is why clock skew bugs showed up when CPU started
> clocking down on the fly to
On 12/07/2010 03:10 PM, Tim wrote:
>
> I'd still check, or simply replace, the battery. Some PCs do weird
> things when their battery goes flat, even though it really ought to work
> fine while the power is on (the CMOS is, usually, powered by the main
> power supply as well as the battery).
I ag
Joe Zeff:
>> If the clock's running consistently slow, try replacing the CMOS
>> battery. The BIOS is set to start doing that when the battery gets
>> low to let you know that it needs changing.
>
Alex:
> I should have mentioned that it's running fast -- really fast. I just
> reset it about a hal
Hi,
> Have you checked the date? ntpd adjusts time by making the clock run
> faster or slower - so if your date is in the past, ntpd may be trying to
> catch up.
> try running "ntpq -p" -- that should show you how far you are from your
> ntp server
I should have mentioned that I did this as well.
On 12/06/2010 04:18 PM, Alex wrote:
> Hi,
>
> What could be the cause of significant clock skew? The PC operated
> fine for quite some time, and either something changed or there is
> something wrong with the motherboard, but the clock could skew an hour
> in less than a 24 hour period. The PC is u
what length are you running? I've seen kernel-xen tick minutes as seconds.
top-posted from gmail on android. apologies.
On Dec 6, 2010 8:13 PM, "Alex" wrote:
> Hi,
>
>>> What could be the cause of significant clock skew? The PC operated
>>> fine for quite some time, and either something changed o
Hi,
>> What could be the cause of significant clock skew? The PC operated
>> fine for quite some time, and either something changed or there is
>> something wrong with the motherboard, but the clock could skew an hour
>> in less than a 24 hour period.
>
> If the clock's running consistently slow,
On 12/06/2010 04:18 PM, Alex wrote:
> What could be the cause of significant clock skew? The PC operated
> fine for quite some time, and either something changed or there is
> something wrong with the motherboard, but the clock could skew an hour
> in less than a 24 hour period.
If the clock's run
Hi,
What could be the cause of significant clock skew? The PC operated
fine for quite some time, and either something changed or there is
something wrong with the motherboard, but the clock could skew an hour
in less than a 24 hour period. The PC is usually completely idle. It
has all regular x86_
10 matches
Mail list logo
