mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: "Brad Campbell" <brad@wasp.net.au>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.16.1 psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1 and ACPI
Date: Mon, 17 Apr 2006 08:22:53 -0400	[thread overview]
Message-ID: <d120d5000604170522q54b4b6ftc263f16a649a99e7@mail.gmail.com> (raw)
In-Reply-To: <44437793.20908@wasp.net.au>

On 4/17/06, Brad Campbell <brad@wasp.net.au> wrote:
>
> Apr 17 14:12:30 bklaptop kernel: psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
> Apr 17 14:12:30 bklaptop last message repeated 4 times
> Apr 17 14:12:30 bklaptop kernel: psmouse.c: issuing reconnect request
>
> I know it's related to ACPI as if I kill all apps that poll the acpi interface the problem goes
> away. My issue is that when I do that, I sometimes forget to plug the machine in when it needs it
> (or suspend it to change the battery) and it winds up dead with no warning. So I *really* need my
> battery monitoring.
>
> I just don't recall having these problems, to this extent with earlier kernels. It's always been
> there, but I guess since I passed about 2.6.13 or thereabouts it has just gotten worse. 2.6.16.1 is
> almost unusable for serious work if I have anything monitoring the battery.
>

I often do you have your apps polling battery? Changing to 1 or 2
minutes might help.

...
> ACPI: Embedded Controller [EC0] (gpe 29) interrupt mode.

You can try changing EC to use polling mode (ec_intr=0) or even try disablig it.

--
Dmitry

  reply	other threads:[~2006-04-17 12:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-17 11:10 Brad Campbell
2006-04-17 12:22 ` Dmitry Torokhov [this message]
2006-04-17 14:01   ` Brad Campbell
2006-04-17 15:16     ` Dmitry Torokhov
2006-04-17 15:42       ` Brad Campbell

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=d120d5000604170522q54b4b6ftc263f16a649a99e7@mail.gmail.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=brad@wasp.net.au \
    --cc=dtor_core@ameritech.net \
    --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

all inboxes | Powered by JetHome®