From: Marc <marvin24@gmx.de>
To: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: clock skew on B/W G3
Date: Sun, 2 Oct 2005 18:46:09 +0200 [thread overview]
Message-ID: <200510021846.09860.marvin24@gmx.de> (raw)
In-Reply-To: <200510011429.45698.marvin24@gmx.de>
Some additions to the previous mail: I was able to isolate the problem to t=
he=20
introduction of a user specificable value of HZ (in include/asm-ppc/parm.h)=
=2E=20
I used a value of 250 while the former default was 1000. Setting it back to=
=20
1000 makes the clock tick right again.
Is the CONFIG_HZ known to be broken on PPC ?
Thanks
Marc
Le Samstag 01 Oktober 2005 14:29, marvin24@gmx.de a =C3=A9crit :
> Hi,
>
> something between 2.6.13-git4 and 2.6.14-git5 makes my clock running ~20%
^^ should be 13 of course=20
> slower. This problem still exists in current kernel versions. Sorry for
> reporting so late, but I hope it would go away while time passes...
>
> As the subject says I have blue/white Apple G3/400. My config I attached.
WARNING: multiple messages have this Message-ID (diff)
From: Marc <marvin24@gmx.de>
To: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: clock skew on B/W G3
Date: Sun, 2 Oct 2005 18:46:09 +0200 [thread overview]
Message-ID: <200510021846.09860.marvin24@gmx.de> (raw)
In-Reply-To: <200510011429.45698.marvin24@gmx.de>
Some additions to the previous mail: I was able to isolate the problem to the
introduction of a user specificable value of HZ (in include/asm-ppc/parm.h).
I used a value of 250 while the former default was 1000. Setting it back to
1000 makes the clock tick right again.
Is the CONFIG_HZ known to be broken on PPC ?
Thanks
Marc
Le Samstag 01 Oktober 2005 14:29, marvin24@gmx.de a écrit :
> Hi,
>
> something between 2.6.13-git4 and 2.6.14-git5 makes my clock running ~20%
^^ should be 13 of course
> slower. This problem still exists in current kernel versions. Sorry for
> reporting so late, but I hope it would go away while time passes...
>
> As the subject says I have blue/white Apple G3/400. My config I attached.
next prev parent reply other threads:[~2005-10-02 16:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-01 12:29 clock skew on B/W G3 marvin24
2005-10-02 16:46 ` Marc [this message]
2005-10-02 16:46 ` Marc
-- strict thread matches above, loose matches on Subject: below --
2005-10-03 14:18 Rune Torgersen
2005-10-03 14:18 ` Rune Torgersen
2005-10-04 6:14 ` Marc
2005-10-04 6:14 ` Marc
2005-10-04 22:10 ` Benjamin Herrenschmidt
2005-10-04 22:10 ` Benjamin Herrenschmidt
2005-10-04 22:14 ` Benjamin Herrenschmidt
2005-10-04 22:14 ` Benjamin Herrenschmidt
2005-10-05 6:34 ` Marc
2005-10-05 6:34 ` Marc
2005-10-04 12:48 ` Paul Mackerras
2005-10-04 12:48 ` Paul Mackerras
2005-10-04 15:15 Rune Torgersen
2005-10-04 15:15 ` Rune Torgersen
2005-10-04 19:14 ` George Anzinger
2005-10-04 19:14 ` George Anzinger
2005-10-04 19:22 Rune Torgersen
2005-10-04 19:22 ` Rune Torgersen
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=200510021846.09860.marvin24@gmx.de \
--to=marvin24@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.