From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Jerome Lacoste <jerome.lacoste@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: i8042 no mouse on resume. (i8042: failed to resume active multiplexor, mouse won't work.)
Date: Thu, 1 Jul 2010 09:24:54 -0700 [thread overview]
Message-ID: <20100701162454.GD4152@core.coreip.homeip.net> (raw)
In-Reply-To: <AANLkTilvxV18Qc2-34GtNmfAIvNL2dtEAPC3iPFNU2Pv@mail.gmail.com>
Hi Jerome,
On Thu, Jul 01, 2010 at 07:00:45AM +0200, Jerome Lacoste wrote:
> [Please CC me]
>
> Hei,
>
> I've had a suspend/resume issue for 3 years: my mouse isn't working
> upon resume. I see this at resume time:
>
> i8042: failed to resume active multiplexor, mouse won't work.
>
> and also some
>
> atkbd.c: Spurious ACK on isa0060/serio0. Some program might be
> trying access hardware directly.
>
> I used to solve it by unbinding/binding my i8042 module after suspend.
> Worked great.
> Now that I've upgraded my distribution once more, the latest kernel
> doesn't expose unbind/bind attributes for the driver.
> See http://marc.info/?l=linux-kernel&m=125585230724962&w=2 for patch
> and thread that (understandably) disabled the feature.
>
> So it looks like there's no workaround left for me to troubleshoot
> this problem. I guess I need to finally fix the original issue !
>
> I've enabled i8042.debug. I've tested the following: boot. go to
> console. echo mem > /sys/power/state, resume, ALT+F7: no mouse on gdm.
>
...
>
> so i8042_set_mux_mode() doesn't seem to work at all
>
> I am running
>
> Linux expresso2 2.6.32-22-generic #36-Ubuntu SMP Thu Jun 3
> 22:02:19 UTC 2010 i686 GNU/Linux
>
> But as far as I can tell, there's no modification to i8042 in that
> kernel (http://packages.ubuntu.com/en/lucid/linux-image-2.6.32-22-generic)
>
> Let me know if you need anything else.
>
> Cheers,
>
> Jerome
>
> For reference,
>
> * the hardware is a Lenovo 3000 N100
We already trying to disable MUX mode on Lenovo 3000 N100, see
drivers/input/serio/i8042-x86ia64io.h:
{
/* Lenovo 3000 n100 */
.matches = {
DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
DMI_MATCH(DMI_PRODUCT_NAME, "076804U"),
},
},
What's in your dmi?
--
Dmitry
next prev parent reply other threads:[~2010-07-01 16:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 5:00 i8042 no mouse on resume. (i8042: failed to resume active multiplexor, mouse won't work.) Jerome Lacoste
2010-07-01 16:24 ` Dmitry Torokhov [this message]
2010-07-01 21:19 ` Jerome Lacoste
2010-07-01 22:28 ` Jerome Lacoste
2010-07-01 22:42 ` Dmitry Torokhov
2010-07-03 8:26 ` Jerome Lacoste
2010-07-03 21:20 ` Dmitry Torokhov
2010-07-04 4:53 ` Henrique de Moraes Holschuh
2010-07-04 5:26 ` Dmitry Torokhov
2010-07-12 14:28 ` Jerome Lacoste
2010-07-12 16:07 ` Dmitry Torokhov
2010-07-02 0:49 ` Henrique de Moraes Holschuh
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=20100701162454.GD4152@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=jerome.lacoste@gmail.com \
--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