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" <mysqlstudent@gmail.com> 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.
>>

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

> I should have mentioned that it's running fast -- really fast. I just
> reset it about a half-hour ago, and it's already two or three minutes
> fast.
>
> Thanks,
> Alex
> --

> users mailing list
> users@lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users

> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

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 usually completely idle. It
> has all regular x86_64 FC13 updates applied.
>
> I've done a bit of searching online, but haven't had much success. How
> can I go about troubleshooting this?
>
> Thanks,
> Alex

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

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

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. I used ntpdate to
sync the time, then ran ntpd. I don't think ntpq ever reported it had
connected to a peer. The clock skews too fast for it to be able to
sync.

> what length are you running? I've seen kernel-xen tick minutes as seconds.

Length? Xen is not involved here in any way. This is a simple install
of FC13 on x86_64.

Could this have something to do with power management?

Thanks,
Alex
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

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 half-hour ago, and it's already two or three minutes
> fast.

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).

--
[tim@localhost ~]$ uname -r
2.6.27.25-78.2.56.fc9.i686

Don't send private replies to my address, the mailbox is ignored. I
read messages from the public lists.



--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

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 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 save power...
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

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 save power...

I don't think the original poster said which clock was skewing.

--
[tim@localhost ~]$ uname -r
2.6.27.25-78.2.56.fc9.i686

Don't send private replies to my address, the mailbox is ignored. I
read messages from the public lists.



--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

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 knows something about the clock it picked
which isn't actually true on the motherboard in question).

>From the kernel-parameters.txt file in the kernel-doc
rpm:

clock= [BUGS=X86-32, HW] gettimeofday clocksource override.
[Deprecated]
Forces specified clocksource (if available) to be used
when calculating gettimeofday(). If specified
clocksource is not available, it defaults to PIT.
Format: { pit | tsc | cyclone | pmtmr }

clocksource= [GENERIC_TIME] Override the default clocksource
Format: <string>
Override the default clocksource and use the clocksource
with the name specified.
Some clocksource names to choose from, depending on
the platform:
[all] jiffies (this is the base, fallback clocksource)
[ACPI] acpi_pm
[ARM] imx_timer1,OSTS,netx_timer,mpu_timer2,
pxa_timer,timer3,32k_counter,timer0_1
[AVR32] avr32
[X86-32] pit,hpet,tsc,vmi-timer;
scx200_hrt on Geode; cyclone on IBM x440
[MIPS] MIPS
[PARISC] cr16
[S390] tod
[SH] SuperH
[SPARC64] tick
[X86-64] hpet,tsc
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines