From: Peter Osterlund <petero2@telia.com>
To: Ricardo Galli <gallir@uib.es>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Synaptics losing sync
Date: 01 Nov 2003 22:04:02 +0100 [thread overview]
Message-ID: <m2k76jssvx.fsf@p4.localdomain> (raw)
In-Reply-To: <200311011751.39610.gallir@uib.es>
Ricardo Galli <gallir@uib.es> writes:
> I've sent this report before.
>
> I repeat it just in case someone found a workaround, and because
> 2.6.0-test9 gives other related errors as well (TSC error):
>
> ...
> Synaptics driver lost sync at 1st byte
> Synaptics driver lost sync at 1st byte
> Synaptics driver lost sync at 1st byte
> Synaptics driver lost sync at 4th byte
> Synaptics driver lost sync at 1st byte
> Synaptics driver lost sync at 1st byte
> Synaptics driver lost sync at 1st byte
> Synaptics driver lost sync at 1st byte
> Synaptics driver resynced.
> Losing too many ticks!
> TSC cannot be used as a timesource. (Are you running with SpeedStep?)
> Falling back to a sane timesource.
> Synaptics driver lost sync at 1st byte
> ...
>
> The laptop is a Dell X200 with APM and cpufreq enabled, and IO-apic
> disabled.
>
> I tested with and w/o preemptive kernel and cpufreq with the same results.
Did you try without APM? My laptop loses many clock ticks if I enable
APM. It works fine with ACPI though.
--
Peter Osterlund - petero2@telia.com
http://w1.894.telia.com/~u89404340
next prev parent reply other threads:[~2003-11-01 21:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-01 16:51 Synaptics losing sync Ricardo Galli
2003-11-01 21:04 ` Peter Osterlund [this message]
2003-11-01 22:47 ` Ricardo Galli
[not found] <N7gI.1K3.9@gated-at.bofh.it>
2003-11-01 22:37 ` 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
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=m2k76jssvx.fsf@p4.localdomain \
--to=petero2@telia.com \
--cc=gallir@uib.es \
--cc=linux-kernel@vger.kernel.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 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).