Re: i8042 no mouse on resume. (i8042: failed to resume active multiplexor, mouse won't work.)

From: Jerome Lacoste
Date: Thu Jul 01 2010 - 18:28:28 EST


On Thu, Jul 1, 2010 at 11:19 PM, Jerome Lacoste
<jerome.lacoste@xxxxxxxxx> wrote:
> On Thu, Jul 1, 2010 at 6:24 PM, Dmitry Torokhov
> <dmitry.torokhov@xxxxxxxxx> wrote:
>> Hi Jerome,
>>
> [...]
>>> * 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?
>
> System Information
>        Manufacturer: LENOVO
>        Product Name: 0768BKG
>        Version: 3000 N100
>
> according to dmidecode

Note: I will try the i8042.nomux option, but can't reboot until tomorrow.

Some information that maybe relevant:

The blacklist used to be broader but was restricted by
https://kerneltrap.org/mailarchive/git-commits-head/2008/9/7/3217784

The discussion is in particular here:
http://lkml.indiana.edu/hypermail/linux/kernel/0809.0/0316.html

which states that the problem for which one didn't want to blacklist was a:

System Information
Manufacturer: LENOVO
Product Name: 076836U
Version: 3000 N100

There seems to be many various versions of that Product Name

http://smolts.org/reports/view_profiles?profile=+3000+N100&search=Submit

I wonder if there are other versions affected by this "regression".

For example

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/86820
points to
http://launchpadlibrarian.net/6494256/dmidecode

Manufacturer: LENOVO
Product Name: 0768B9G
Version: 3000 N100

which is probably also affected

It would be nice if the message that displays "failed to resume active
multiplexor, mouse won't work." could also print out the relevant dmi
information.

That way one could use google to find potentially affected systems :)

Cheers,

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