From: "Szymon Acedański" <accek@poczta.gazeta.pl>
To: Ruben Puettmann <ruben@puettmann.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Synaptics losing sync
Date: Mon, 3 Nov 2003 18:13:24 +0100 [thread overview]
Message-ID: <200311031813.24701.accek@poczta.gazeta.pl> (raw)
In-Reply-To: <20031103132557.GD27206@puettmann.net>
On Monday 03 November 2003 14:25, you wrote:
> On Sun, Nov 02, 2003 at 10:48:33AM +0100, Szymon Aceda?ski wrote:
>
> hy,
>
> > "Losing too many ticks" exists when I'm running with cpufreq
> > [p4_clockmod] and clock=tsc (default). This is because of rescaling TSC
> > pitch by cpufreq, I think. If I specify in bootloader clock=hpet, problem
> > disappears. [Am I doing right?]
>
> If I boot with clock=hpet the cpu MHz in cat /proc/cpuinfo is 0.
Oh, yes. HPET timer needs ACPI support to work (also HPET is not present on
many machines). You can probably find 'Warning: clock= override failed' in
your dmesg. The default timer is then set to PIT. Determination of CPU clock
when using PIT is not implemented in the kernel, so it's reported as zero in
/proc/cpufreq. You may also find some patches around the LKML adding support
for ACPI timer, but it needs ACPI itself. I didn't try it.
Szymon
next prev parent reply other threads:[~2003-11-03 17:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <N7gI.1K3.9@gated-at.bofh.it>
2003-11-01 22:37 ` Synaptics losing sync Ruben Puettmann
2003-11-02 9:48 ` Szymon Acedański
2003-11-03 13:25 ` Ruben Puettmann
2003-11-03 17:13 ` Szymon Acedański [this message]
2003-11-01 16:51 Ricardo Galli
2003-11-01 21:04 ` Peter Osterlund
2003-11-01 22:47 ` Ricardo Galli
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=200311031813.24701.accek@poczta.gazeta.pl \
--to=accek@poczta.gazeta.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=ruben@puettmann.net \
/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;
as well as URLs for NNTP newsgroup(s).