i8042 mouse & keyboard often becomes completely unresponsive

[Jerome Lacoste]

My keyboard and mouse often stop working. It usual happens when I am typing something. This happens _very_ often (happens to me ca once per hour).

Steps:
1. type as usual

What happens
Keyboard becomes completely unresponsive (CAPS, NUMLOCK not working). Last key/key combination typed gets repeated (appears many times on xterm or editor, etc...)

Expected:
Keyboard keeps functionning properly.

Known work-around(s):
The machine is still running properly and I usualy have 2 solutions to solve the issue:
* perform a suspend/resume cycle (note: I use the following default kernel options in grub # defoptions=quiet splash acpi_sleep=s3_bios i8042.nomux i8042.reset ). This of course tends to break my network
* ssh into the box and force a keyboard driver reload using:

$ cat local/bin/fixmouseaftersuspend
echo -n "i8042" > /sys/bus/platform/drivers/i8042/unbind
echo -n "i8042" > /sys/bus/platform/drivers/i8042/bind

(this script comes from #214985)

This solves my problem. There's never been anything interesting in dmesg (no i8042 message related at all)

Misc:
* Hardware: Lenovo 3000 N100.
* Distrib: Hardy as of 13/Apr/2008

[Jerome Lacoste (jerome-lacoste)]

Today, resuming from suspend (albeit a longer one than usually, not sure if that affects), didn't reproduce this problem. First time in a long time. On the other side, this time wireless didn't come up and I had to do this:

rmmod iwl3945
rmmod iwlwifi_mac80211
modprobe iwl3945

to fix it. Note: wireless was I think disconnected when I put the machine to sleep.

I will try to see if both problems always exclude each other. I will also try to see if I can reproduce the wireless doesn't come up problem. I used to experience it, but it appears that I forgot to open an issue in launchpad.

[Jerome Lacoste (jerome-lacoste)]

This happened for the second time. This time ca 20 min. after a resume from suspend.

Fixed again with my local/bin/fixmouseaftersuspend ran after ssh'ding into my machine.

Again, nothing special in dmesg that would indicate that the keyboard driver failed:

 [ 145.968159] wlan0: authenticate with AP 00:18:f8:6d:30:2d
 [ 145.969758] wlan0: RX authentication from 00:18:f8:6d:30:2d (alg=0 transaction=2 status=0)
 [ 145.969766] wlan0: authenticated
 [ 145.969769] wlan0: associate with AP 00:18:f8:6d:30:2d
 [ 145.971504] wlan0: RX AssocResp from 00:18:f8:6d:30:2d (capab=0x431 status=0 aid=716)
 [ 145.971511] wlan0: associated
 [ 145.975234] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
 [ 165.967088] wlan0: no IPv6 routers present
+[ 1413.972710] serio: i8042 KBD port at 0x60,0x64 irq 1
+[ 1413.972726] serio: i8042 AUX port at 0x60,0x64 irq 12
+[ 1413.992858] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio4/input/input11
+[ 1414.842355] Synaptics Touchpad, model: 1, fw: 6.2, id: 0x1a0b1, caps: 0xa04753/0x200000
+[ 1414.914583] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio5/input/input12

(the new lines appear after the driver is reactivated)

[Jerome Lacoste (jerome-lacoste)]

This happened again. This time I was using CTRL+ALT+RIGHT to switch workspace.
I just triggered the key combination once but the desktop was switched from my left worspace to my rightmost workspace (i.e. 3 workspaces to the right). and got stuck there. The workspace switcher indicator that appears didn't disappear. I remember now that one of my other keyboard/mouse issue was very similar.

I once again ssh'd into and did my echo trick to fix the mouse/keyboard. Still no message in dmesg. Nothing under Xorg.0.log neither.

I highly suspect this to be compiz related somehow.

[Jerome Lacoste (jerome-lacoste)]

This happened again. This time I was using CTRL+ALT+RIGHT to switch workspace.
I just triggered the key combination once but the desktop was switched from my left worspace to my rightmost workspace (i.e. 3 workspaces to the right). and got stuck there. The workspace switcher indicator that appears didn't disappear. I remember now that one of my other keyboard/mouse issue was very similar.

I once again ssh'd into and did my echo trick to fix the mouse/keyboard. Still no message in dmesg. Nothing under Xorg.0.log neither.

I highly suspect this to be compiz related somehow.

Note: I also sometimes manage to fix it by suspending and resuming again, without applying my echo script.

[Leann Ogasawara (leannogasawara)]

Hi Jerome,

Thanks for the report and the updates. You mentioned you think this may be related to compiz. Have you tried disabling compiz to see if the issue disappears. Also, I'm curious if any errors are showing up in /var/log/syslog? Could you also include the output of 'cat /proc/version_signature' as well as attach your full dmesg output after you experience this issue?

I'm also going to file this bug against the Hardy kernel source package 'linux' for now. Making sure bugs are assigned to the proper package help ensure that bugs are seen by the appropriate developers. Thanks.

Thanks.

[Jerome Lacoste (jerome-lacoste)]

Problem happening right now, ca 10 minutes after a resume from suspend.

Nothing in syslog / dmesg.

$ cat version_signature
Ubuntu 2.6.24-16.30-generic

The keyboard got stuck while typing 'less' on a terminal and it keeps printing 's' .... Compiz is still enabled. I will disable it from now on and see if this happens again.

[Jerome Lacoste (jerome-lacoste)]

several batches of proc_interrupts created every 10 seconds in each situation:

* _1_ problem occuring. Both firefox and gnome-terminal present on screen. gnome_terminal displaying 's' continuously without me touching the keyboard. Mouse & keyboard unresponsive

* _2_ problem occuring. Firefox killed. gnome-terminal still present on screen. gnome_terminal still displaying 's' continuously without me touching the keyboard. Mouse & keyboard unresponsive

* _3_ problem occuring. gnome-terminal killed. nautilus now taking 100% CPU (one of my 2 cores). Not sure if it took 100% before. Mouse & keyboard unresponsive

* _4_ after a suspend/resume, problem fixed.

[Jerome Lacoste (jerome-lacoste)]

As explained in comment above, at some point nautilus got 100%.Here's a top output showing the issue. Didn't think of attaching gdb... Next time will do.

[Jerome Lacoste (jerome-lacoste)]

I've added as much information as possible. I've asked on #ubuntu for what else I should provide but got no answer.

I am now using compiz and will notify if I get the problem again.

I change the status back to New.

[Jerome Lacoste (jerome-lacoste)]

I meant "I am not using compiz anymore"

[Jerome Lacoste (jerome-lacoste)]

The problem just happened and this time I wasn't running compiz. So my gut feeling was wrong and this seems completely kernel related.

What's the next step ?

Should I try to enable i8042.debug ? Is there an Ubuntu kernel available with kgdb ? (maybe a patched 2.6.25 from universe ?)

Any idea ?

[Stefan Bader (smb)]

Is there a specific reason you run with active multiplexing disabled? i8042.debug might help to see what happens during the times the keyboard seems to be stuck. Have you tried running with nosmp or with acpi_apic_instance=2?

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Jerome Lacoste (jerome-lacoste)]

I have some more information

* the problem persists in Ibex. I've upgraded some weeks ago and keep getting the issue every now and then
* the problem seems to be X and kernel related.

Today I experienced the problem while running with a second screen (using Twinview) and keyboard/mouse (USB).

The kaptop keyboard/mouse 'died' as usual, but the external keyboard still worked. That allows me to run my script to fix the laptop internal keyboard.

Here's the information from Xorg.0.log before I ran my script:

[...]
(II) Video Bus: Device reopened after 10 attempts.
(II) Video Bus: Device reopened after 10 attempts.
(II) HID 04d9:0499: Device reopened after 10 attempts.
(**) HID 04d9:0499: YAxisMapping: buttons 4 and 5
(**) HID 04d9:0499: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) LITE-ON Technology USB NetVista Full Width Keyboard.: Device reopened after 10 attempts.
(II) AT Translated Set 2 keyboard: Device reopened after 10 attempts.
(II) Macintosh mouse button emulation: Device reopened after 10 attempts.
(**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5
(**) Macintosh mouse button emulation: EmulateWheelButton: 4, EmulateWheelInertia: 10,

Here's the information from Xorg.0.log after I ran my script:

(EE) AT Translated Set 2 keyboard: Read error: No such device
(EE) AT Translated Set 2 keyboard: Device has changed - disabling.
(WW) AT Translated Set 2 keyboard: Release failed (Invalid argument)
(II) config/hal: removing device AT Translated Set 2 keyboard
(II) AT Translated Set 2 keyboard: Close
(II) UnloadModule: "evdev"
(II) config/hal: removing device SynPS/2 Synaptics TouchPad
(II) UnloadModule: "synaptics"
(II) config/hal: Adding input device SynPS/2 Synaptics TouchPad
(II) Synaptics touchpad driver version 0.15.2
(II) SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5472
(II) SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4448
(**) Option "Device" "/dev/input/event9"
(--) SynPS/2 Synaptics TouchPad touchpad found
(**) SynPS/2 Synaptics TouchPad: always reports core events
(II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD)
(II) SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5472
(II) SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4448
(--) SynPS/2 Synaptics TouchPad touchpad found
(II) config/hal: Adding input device AT Translated Set 2 keyboard
(**) AT Translated Set 2 keyboard: always reports core events
(**) AT Translated Set 2 keyboard: Device: "/dev/input/event1"
(II) AT Translated Set 2 keyboard: Found keys
(II) AT Translated Set 2 keyboard: Configuring as keyboard
(II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) AT Translated Set 2 keyboard: xkb_rules: "evdev"
(**) Option "xkb_model" "pc105"
(**) AT Translated Set 2 keyboard: xkb_model: "pc105"
(**) Option "xkb_layout" "no"
(**) AT Translated Set 2 keyboard: xkb_layout: "no"
(**) Option "xkb_options" "lv3:ralt_switch"
(**) AT Translated Set 2 keyboard: xkb_options: "lv3:ralt_switch"

Attached, the full commented Xorg.0.log

[Jerome Lacoste (jerome-lacoste)]

> Is there a specific reason you run with active multiplexing disabled?

I think I've added that to solve a suspend/resume issue. Maybe it's not necessary anymore

> i8042.debug might help to see what happens during the times the keyboard seems to be stuck.

Should I enable it at boot ?

> Have you tried running with nosmp or with acpi_apic_instance=2?

No. I will have to try. I will start with the i8042.debug and re-enabling the multiplexing.

And as to the kernel question, I am now running kernel:

 Linux expresso2 2.6.27-4-generic #1 SMP Wed Sep 24 01:30:51 UTC 2008 i686 GNU/Linux

Thanks for your help

[Leann Ogasawara (leannogasawara)]

Hi Jerome,

Intrepid's final release is set to come out in a few days. It would be great if you could confirm if this is still an issue with this newest release. Thanks.

[Jerome Lacoste (jerome-lacoste)]

On Wed, Oct 29, 2008 at 3:31 AM, Leann Ogasawara <email address hidden> wrote:
> Hi Jerome,
>
> Intrepid's final release is set to come out in a few days. It would be
> great if you could confirm if this is still an issue with this newest
> release. Thanks.
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete

I can confirm that this is still a problem.

It's even more a problem that somtimes I suspend doesn't work (e.g.
when transmission bittorrent is running, or because of another issue).
And if I don't have access to another computer to ssh into my box, I
am then forced to hard stop the machine.

I am strongly considering to pay for support to solve this issue. Or
find an appropriate work-around.

Jerome

[Jerome Lacoste (jerome-lacoste)]

Note: when using an external laptop/mouse, only the embedded screen/mouse is affected.

[Jerome Lacoste (jerome-lacoste)]

This is still a problem on Intrepid. Because of #292929, I also now am unable to suspend. THis is going to kill my machine in the long run. Can we make this issue go further ?

[Jerome Lacoste (jerome-lacoste)]

And I will start by disabling multiplexing and enabling i8042.debug
J

[Jerome Lacoste (jerome-lacoste)]

I meant "reenabling active multiplexing and enabling i8042.debug"

[Jerome Lacoste (jerome-lacoste)]

If I remove "i8042.nomux i8042.reset" from my kernel, the mouse doesn't work after supend.
I will try with i8042.reset only...

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Triaged a while ago but has not had any updated comments for quite some time. Please let us know if this issue remains in the current Ubuntu release, http://www.ubuntu.com/getubuntu/download . If the issue remains, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]