From: Alexey Starikovskiy <astarikovskiy@suse.de>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Jiri Kosina <jkosina@suse.cz>,
linux-input@vger.kernel.org,
Carlos Tonussi <tonussi@farmaco.ufsc.br>
Subject: Re: Need for 'nomux' has been rising lately ...
Date: Tue, 14 Oct 2008 19:59:01 +0400 [thread overview]
Message-ID: <48F4C1C5.9090006@suse.de> (raw)
In-Reply-To: <20081014111522.ZZRA012@mailhub.coreip.homeip.net>
Dmitry Torokhov wrote:
> Hi Jiri,
>
> On Tue, Oct 14, 2008 at 04:55:22PM +0200, Jiri Kosina wrote:
>> Hi Dmitry,
>>
>> lately, I have been seeing a couple of bug reports in which touchpad of
>> certain notebooks misbehaved, and i8042.nomux solved the problem. Most
>> recently, this happened on [1]. Do you have any idea what might be the
>> cause of the need for nomux rising so much lately? Apparently, some older
>> kernels behaved correctly even without this workaround, at least on Acer
>> Aspire 5710, as referenced in the bugreport.
>>
>
> I am always happy to blame ACPI code (especially EC) for bad
> iteraction with input devices ;), especially since there weren't any
> significant changes to i8042 in any recent kernels. Do you think the
> person reporting the failure on Acer could try bisecting it? Could
> ALexey Starikovskiy have any ideas whether there is bad EC iteractions
> stopping timely delivery of mouse interrupts?
>
There was an issue with EC interrupt storm on several Acer notebooks lately,
hopefully solved (bug 11549).
Symptoms could be that keyboard/mouse are slow, missing keys, etc.
I suggest you should try the patch in 11549, or acpi-test tree, and see if your
problem goes away...
Regards,
Alex.
next prev parent reply other threads:[~2008-10-14 15:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 14:55 Need for 'nomux' has been rising lately Jiri Kosina
2008-10-14 15:24 ` Dmitry Torokhov
2008-10-14 15:59 ` Alexey Starikovskiy [this message]
2008-10-16 0:10 ` Jiri Kosina
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=48F4C1C5.9090006@suse.de \
--to=astarikovskiy@suse.de \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=tonussi@farmaco.ufsc.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.