'psmouse.c: TouchPad at isa0060/serio1/input0 lost sync at byte 1'

Bug Description

Feisty Beta 1.

I have a compaq presario 730us laptop. Duron 1Ghz, 256mb ram.

When I plug in my PS2 optical mouse it does not work. The mouse lights up and the trackpad continues to work however when I move the mouse around the system slows down and the trackpad doesn't work.

If I have the device manager open I can see the entries around the trackpad and ps2 changing when I move the mouse.

Thanks for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), 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.
For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance!

Linux compaq 2.6.20-12-generic #2 SMP Wed Mar 21 20:55:46 UTC 2007 i686 GNU/Linux

There has been a kernel update for Feisty since you first reported your bug. Could you please update your kernel and report back if it is still an issue? Thanks again.

updated to .13 The bug is still present.

Thanks

Thanks Brian, it looks like you found the source of the problem. Any chance this will be fixed before the feisty release?

Thanks

Thanks for the bug report, I know it's annoying for my laptop has the very same problem. As far as I can tell it looks like either one of two things, either the synaptics driver has issues, or the mouse and wireless card share an IRQ or resource and affect each other. Either way this issue is really frustrating and I've looked far and wide for an appropriate fix. I can say at least on my end that the new releases work better then the earlier versions. Also decreasing the sensitivity of the mouse helped some as well. However this is a known issue, and to help reduce duplication of effort I am flagging this as a duplicate of bug #34501 If you feel that this is mistaken feel free to re-open the ticket.

Thanks,
~ Mike

Actually I don't know if it is the same issue. My mouse will not work at all. It's not like I can change some settings and it works better. With the mouse plugged into the PS2 port, it does not move. If I move the mouse it will lock up the pointer for a few seconds. Only after those few seconds does the touchpad respond again.

I have been through 3 kernel updates since I posted this and it is still broken.

Linux compaq 2.6.20-15-generic #2 SMP Sat Apr 14 00:54:01 UTC 2007 i686 GNU/Linux

Okay so here is what is happening in device manager.

When just using the touchpad there is an entry for

Platform Device (i8042)
--i8042 AUX port
----SynPS/2 Synaptics Touchpad
--i8042 KBD port
----AT Translated Set 2 Keyboard

However if I start moving my ps2 connected mouse around the CPU goes to 100% and the entry changes to:

Platform Device (i8042)
--i8042 AUX port
--i8042 KBD port
----AT Translated Set 2 Keyboard

While it's like this, the pointer is locked up. As soon as it changes back to the first entry I can use the touchpad again.

Let me know if you need anymore info.

The reason why I believe this is the same bug is on my machine when the mouse freaks out I also get the following in "dmesg" It appears that the touchpad is sending more information then psmouse can handle. and it resets and when that happens the mouse goes crazy for a couple of seconds. I really hope someone figures this out because I've found bug reports for it for over a year. Hope this helps.

[321243.124000] psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
[321243.124000] psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
[321243.140000] psmouse.c: TouchPad at isa0060/serio4/input0 - driver resynched.
[321243.144000] psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
[321243.144000] psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
[321243.148000] psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
[321243.148000] psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
[321243.152000] psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
[321243.152000] psmouse.c: issuing reconnect request

I have a HP laptop and it is doing the same thing for me. I am running the latest Feisty

I had problems getting my trackpoint on a thinkpad R31 run with the same problems and was a problem with the intel chipset and newer linux kernels.

Giving a kernel parmeter did it: "i8042.nomux=1"

Edit your /boot/grub/menu.lst
Go to the line that starts with "# kopt= ... " and add "i8042.nomux=1" to the END.

Mike Dahlgren, it is not a good idea to close this bug report as a duplicate of #34501.
Bug #34501 has zero information from the bug reporter and is probably assigned to the wrong package, which makes it a bad metabug candidate.
Please leave this bug report open since it provides at least the minimal debugging information needed and is assigned to the right package.

I have an Acer 9301 Wmsi which exhibted this exact problem. however I have also found an exact solution to which makes perfect sense to me.

Along with the psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte messages I was also getting

atkbd.c: Spurious NAK on isa0060/serio0. Some program might be trying access hardware directly.

I tried various workarounds including what was suggest above with no success. I tried the nvidia timing paramter and that too had no effect. So then it occured to me that the 2 might be related. So what is it that actually access the keyboard apart from X. And I knew what it was. The ledd functions are designed to program the keyboard for various functions. And there was a kernel parameter that fitted that usage. In another thread somewhere concerning the spurious ack ( http://kerneltrap.org/node/5898 ) someone suggested using i8042.panicblink=0 which no longer is a parameter in my 2.6.23 kernel. however i8042.dumbkbd is. And by enabling that it does try to send anything to the keyboard at all.

so I set i8042.dumbkbd=1 in the kernel parameters and not only did the spurious ACk error disappear but the psmouse lost sync messages too.

So I suggest people attempt that and see if it solves they issue. If so then it ought to be noted that the i8042 driver is buggy on certain motherboards and should not attempt to write anything to the keyboard.

Hope that helps.

This problem appeared for me when I upgraded to Feisty, together with the keyboard bug 124406 (https://bugs.launchpad.net/ubuntu/+bug/124406) I don't know if they are related, but they are both annoying!

Changing the linux version to 2.6.22 - as the problem persists in that version.

The same bug was detected in the ppc side of things, bug #32877. I marked this bug as the duplicate because that one was discovered first, although this one seems to have more progress on it.

No the main bug should be the one with the most info, not the one that was reported first.

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

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.