ThinkPad R40e Keyboard/Mouse/Trackpoint regularly unresponsive on Feisty Release

[Msakaji]

The keyboard and trackpoint/mouse of a ThinkPad R40e running the Ubuntu Feisty release become irritatingly unresponsive at regular short intervals lasting for a period of about 10 seconds, after which there is a 20-30 second period of normal operation before the problem recurs. Characters typed while the keyboard is unresponsive do not appear after the keyboard resumes operation.

The system takes an excessive time to boot, wavering noticably during "Loading ACPI modules" and "Starting Hardware abstraction layer hald".

The bug's symptoms occur in both graphical and text mode.

This problem is reported by one user to have only occurred on versions of Feisty (herd#) with kernel versions 2.6.20-2-generic and later.

Adding the line "acpi=off" to the GRUB bootloader does NOT resolve the problem.

Discussion of this problem occurred on the ubuntu forums at http://ubuntuforums.org/showthread.php?t=402926

[Jamsven1984 (knafelj)]

I have the same problem with using a PS/2 keyboard with Feisy on my Desktop computer.

[Dan O'Huiginn (daniel-ohuiginn)]

Thanks for this report. Please include the following additional information, as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
4. Please run 'sudo dmidecode > dmidecode.log' and attach the resulting 'dmidecode.log' to this bug report
5. Try to hibernate/suspend and then restart the system and attach the file /var/log/kern.log.0

For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance!

[Msakaji (anthrolion)]

1)
msakaji@stinkpad:~$ uname -a
Linux stinkpad 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux

2, 3, 4) attached

5) The system suspends but then does not awaken. I had to remove the battery and disconnect the AC adapter.

NB: An external cordless USB mouse (Logitech V200 Cordless Notebook Mouse) is not affected by this behaviour and operates normally.

[m0laria (m0laria)]

I also have this problem.

1.) Linux m0laria-laptop 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux

[Dan O'Huiginn (daniel-ohuiginn)]

Thanks for providing that information.

[Msakaji (anthrolion)]

Today I noticed an unusual message displayed on booting my ThinkPad R40e - This hasn't appeared before:

[...]
Starting Hardware abstraction layer hald
[ 127.281517] serial8250: too much work for irq11 <--- did not show up before
[...]

I hope that helps. The machine continued to boot slowly as always but then successfully went into graphical mode and provided the login screen.

[Elife (pepe-putois)]

I have the same problem.
My IBM r40e freeze two times at boot :

- Loading ACPI modules
- Starting Hardware abstraction layer hald

And sometimes :
Starting Hardware abstraction layer hald
[ 127.281517] serial8250: too much work for irq11

The keyboard have the same problem too.

uname -a :
Linux arthur-laptop 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux

Sorry for my english.

[Martin Garton (martingarton)]

Is there any news on this? I'm seeing the same problem. I'm willing to help out if there is anything I can do. (testing etc?)

[Mark Doughty (email-markdoughty)]

This sounds like it is the same bug as here:

https://bugs.launchpad.net/ubuntu/+source/casper/+bug/107516

and here:

http://bugzilla.kernel.org/show_bug.cgi?id=8246

Try adding ec_intr=0 to your kernel options in grub. For me this made everything more responsive but it is only a workaround. If this works for you guys then this bug should probably be marked as a duplicate. Unfortunately none of these bugs seem to have much activity so any extra information that can be supplied will probably be helpful.

[Martin Garton (martingarton)]

I tried upgrading to gutsy pre-release to see if it has been fixed, but unfortunately not and there's no sign of it being fixed before the final release either.

In the absence of anyone looking at this, or even giving instructions on how I can help out myself, it looks like I'm going to have to change back to dapper or try another distro.

[Mark Doughty (email-markdoughty)]

Did you try adding ec_intr=0 to your kernel boot options? I have a thinkpad R40e as well and adding that has been a good workaround!

[Elife (pepe-putois)]

I can't test, I give this laptop.

[Martin Garton (martingarton)]

ec_intr=0 does work as a workaround, but can hardly be considered a fix! (unless it is inserted into grub.conf automatically during install for example)

[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.

[Martin Garton (martingarton)]

After digging out this laptop and testing the intrepid pre-release on it, I can confirm that the problem is fixed for me.

[Rolf Leggewie (r0lf)]

Thank you for reporting back. Setting to "Fix released".

[Rolf Leggewie (r0lf)]

I just realized that Martin was not the original report of the problem. Msakaji, please feel free to reopen this issue should you please experience it.