Massive clock drift on Cobalt Raq2 after upgrade to 2.6.18-1-r5k-cobalt

Massive clock drift on Cobalt Raq2 after upgrade to 2.6.18-1-r5k-cobalt

[Dominique Quatravaux]

Dear MIPS hackers,

The subject line pretty much says it all: between yesterday morning and
both my system clock and my uptime increased by about 2 days while only
10 hours actually elapsed... I was previously using kernel
2.4.27-r5k-cobalt (also from Debian) and the clock worked fine.

Maybe this is related to the following:

kilimandjaro:~# zgrep CONFIG_HZ= /proc/config.gz
CONFIG_HZ=250
kilimandjaro:~# grep periodic_freq /proc/driver/rtc
periodic_freq   : 1024

which from my ignorant POV would mean that the clock runs about 5 times
too fast?

How do I go about correcting the problem? I upgraded the kernel without
powering off, should I power-cycle now?

Many thanks in advance from a few days in the future :-)

-- 
<< Tout n'y est pas parfait, mais on y honore certainement les jardiniers >>

			Dominique Quatravaux <dom@kilimandjaro.dyndns.org>

Re: Massive clock drift on Cobalt Raq2 after upgrade to 2.6.18-1-r5k-cobalt

[Martin Michlmayr]

* Dominique Quatravaux <dom@kilimandjaro.dyndns.org> [2006-10-24 12:36]:
> The subject line pretty much says it all: between yesterday morning and
> both my system clock and my uptime increased by about 2 days while only
> 10 hours actually elapsed... I was previously using kernel
> 2.4.27-r5k-cobalt (also from Debian) and the clock worked fine.
> 
> How do I go about correcting the problem? I upgraded the kernel without
> powering off, should I power-cycle now?

You need to upgrade to 2.6.18-1-r5k-cobalt version 2.6.18-3 which
contains a fix for this.
-- 
Martin Michlmayr
http://www.cyrius.com/

Re: Massive clock drift on Cobalt Raq2 after upgrade to 2.6.18-1-r5k-cobalt

[Ralf Baechle]

On Tue, Oct 24, 2006 at 12:36:29PM +0200, Dominique Quatravaux wrote:

This was fixed about 3 weeks ago in linux-mips.org 2.6.19-rc2 / 2.6.18.1.
Debian's kernel is probably lagging a bit.

  Ralf

Re: Massive clock drift on Cobalt Raq2 after upgrade to 2.6.18-1-r5k-cobalt

[Dominique Quatravaux]

Martin Michlmayr a écrit :
> You need to upgrade to 2.6.18-1-r5k-cobalt version 2.6.18-3 which
> contains a fix for this.
>   
Thanks a bunch. This time around I managed to upgrade the kernel without
a lengthy trip to the suburbs :-)

Best regards, Dom

-- 
<< Tout n'y est pas parfait, mais on y honore certainement les jardiniers >>

			Dominique Quatravaux <dom@kilimandjaro.dyndns.org>