From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Dmitrij Bogush <dmitrij.bogush@gmail.com>
Cc: sboyce@blueyonder.co.uk, linux-kernel@vger.kernel.org
Subject: Re: Touchpad errors
Date: Tue, 2 Aug 2005 15:29:49 -0500 [thread overview]
Message-ID: <d120d50005080213296fac871e@mail.gmail.com> (raw)
In-Reply-To: <2ac89c700508021314f42da6a@mail.gmail.com>
On 8/2/05, Dmitrij Bogush <dmitrij.bogush@gmail.com> wrote:
> Hi.
> I have the same issue on Acer Aspire 1520 notebook. On SuSE 9.3 system
> can not boot with acpi=off.
> In 2.6.13-rc4-git4 this crazy touchpad jumps reports as:
>
> warning: many lost ticks.
> Your time source seems to be instable or some driver is hogging interupts
> rip handler_IRQ_event+0x20/0x60
>
> and sometimes I can see
>
> psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte N
>
> This happens when some software check battery state or current cpu
> rate too often.
>
Yes, that would do it. psmouse module drops received byte if it is
delayed for more than 0.5 sec. On some machines getting batetry info
takes a long time and all the time is spent in BIOS with interrupts
disabled. That is why the data is split between state and info - one
is static and takes much longer to access and other is more "dynamic"
and is cheaper to access. Unfortunately some usespace tools check both
and do that like every second.
You may try to talk to ACPI people; also I recommend setting battery
polling interval to something sane, like 1 minute, and make sure your
tool does not touch "info" file - that should help a bit.
--
Dmitry
next prev parent reply other threads:[~2005-08-02 20:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-02 12:12 Touchpad errors Sid Boyce
2005-08-02 14:22 ` Dmitry Torokhov
2005-08-02 20:14 ` Dmitrij Bogush
2005-08-02 20:20 ` Lee Revell
2005-08-02 22:46 ` Sid Boyce
2005-08-02 20:29 ` Dmitry Torokhov [this message]
2005-08-02 21:58 ` Dmitrij Bogush
2005-08-02 22:06 ` Sid Boyce
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=d120d50005080213296fac871e@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=dmitrij.bogush@gmail.com \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sboyce@blueyonder.co.uk \
/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