From: Szymon =?iso-8859-2?q?Aceda=F1ski?= <accek@poczta.gazeta.pl>
To: ruben@puettmann.net
Subject: Re: Synaptics losing sync
Date: Sun, 2 Nov 2003 10:48:33 +0100
User-Agent: KMail/1.5
References: <N7gI.1K3.9@gated-at.bofh.it> <E1AG4NH-0006xZ-00@baloney.puettmann.net>
In-Reply-To: <E1AG4NH-0006xZ-00@baloney.puettmann.net>
Cc: linux-kernel@vger.kernel.org
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200311021048.33698.accek@poczta.gazeta.pl>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1174
Lines: 32

Hi!

On Saturday 01 November 2003 23:37, Ruben Puettmann wrote:
> > ...
> > 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
> > ...
> >

I can observe the same "Synaptics lost sync" messages on Acer TravelMate 242XC 
with ACPI enabled (without APM even compiled) on 2.6.0-test[0-9]. But I 
silently ignore these messages - touchpad works ok. I use an USB mouse, but 
messages appear even without it plugged.

"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?]

I can provide more information if somebody is interested.

Cheers
Szymon
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/