Comment 90 for bug 990260

(In reply to comment #75)
> This patch has not helped me, too. Have to throw the laptop in the trash :(

[ 2.327464] i8042: [308] 91 -> i8042 (command)
[ 2.327733] i8042: [309] 66 -> i8042 (parameter)
[ 2.330645] i8042: [309] fe <- i8042 (interrupt, 3, 12)
[ 2.330652] i8042: [309] 91 -> i8042 (command)
[ 2.330876] i8042: [309] 88 -> i8042 (parameter)
[...]
[ 4.825925] i8042: [934] 91 -> i8042 (command)
[ 4.826090] i8042: [934] f3 -> i8042 (parameter)
[ 4.829576] i8042: [934] fc <- i8042 (interrupt, 3, 12)

  According to the above log, driver failed to detect the hardware because command
88 timed out.

  I'm afraid that this patch won't help you as the problem you're running into
seems to be EC related. There are a few MUX error in your log:

[ 1.227636] i8042: [33] 90 -> i8042 (command)
[ 1.228579] i8042: [33] f2 -> i8042 (parameter)
[ 1.233864] i8042: [35] MUX error, status is 25, data is fc
[ 1.233875] i8042: [35] fe <- i8042 (interrupt, 2, 12, timeout)
[ 1.233931] i8042: [35] 90 -> i8042 (command)
[ 1.235031] i8042: [35] ed -> i8042 (parameter)
[ 1.240302] i8042: [36] MUX error, status is 25, data is fc
[ 1.240313] i8042: [36] fe <- i8042 (interrupt, 2, 12, timeout)

  Not sure if there are any other i8042 knobs to workaround this problem. Perhaps
Dmitry can shed some light for us?