Bug 8740
Summary: | Synaptics Touchpad lost sync and becomes unusable | ||
---|---|---|---|
Product: | Drivers | Reporter: | Chris Desjardins (cddesjardins) |
Component: | Input Devices | Assignee: | drivers_input-devices |
Status: | REOPENED --- | ||
Severity: | normal | CC: | aaron.lu, alpine.art.de, andre.miras, aravind.appan, dietrichmathias, dmitry.torokhov, jrnieder, jsvaughan, kernel, klamm2001, lenb, mail, merlijn, mezin.alexander, mozilla, synthead, taur |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 3.2.20 | Subsystem: | |
Regression: | Yes | Bisected commit-id: | |
Bug Depends on: | |||
Bug Blocks: | 9147, 56331 | ||
Attachments: | legolas558.devices |
Description
Chris Desjardins
2007-07-12 09:55:06 UTC
Does it help if you boot with "ec_intr=2" on the kernel command line? What about acpi=off? Neither ec_intr=2 nor acpi=off helped. The problem was still occurring. FYI, the laptop I am using is a Lenovo 3000 n100. Thanks for the prompt response! Chris Ok, so you are saying that 2.6.17 was ok but since 2.6.18 things went bad? COuld you try narrow it down to a specific 2.6.18-rcX release? Sorry. Post-2.6.18 it seemed to go bad. However, I just bought this laptop a few months ago and the 2.6.18 worked relatively well. I didn't test any kernel earlier than 2.6.18. The kernel 2.6.18-4-686 in Debian Etch worked well here but because of lack of support for brightness and other hardware I upgraded to the 2.6.22-1 kernel. I experienced some issues with losing sync bytes in 2.6.18-4 but not like in the 2.6.22-1 kernel. It froze up but very rarely. Also I do not believe this is an issue of broken hardware as my laptop is very new. Cheers, Chris Hmm. Do you really have external mouse attached? Or do you have only touchpad and kernel is confused? On Tuesday 17 July 2007 10:14:54 am you wrote: > http://bugzilla.kernel.org/show_bug.cgi?id=8740 > > > > > > ------- Comment #6 from dtor@insightbb.com 2007-07-17 08:20 ------- > Hmm. Do you really have external mouse attached? Or do you have only > touchpad and kernel is confused? I have a Synaptics Touchpad and when my mouse becomes unresponsive I use a usb mouse. No, I mean external PS/2 mouse? On Tuesday 17 July 2007 03:52:52 pm you wrote: > http://bugzilla.kernel.org/show_bug.cgi?id=8740 > > > > > > ------- Comment #8 from dtor@insightbb.com 2007-07-17 13:58 ------- > No, I mean external PS/2 mouse? There is no external PS/2 mouse. I just have my built-in Synaptics Touchpad and the usb mouse. I don't believe it's being confused by the mouse as this is occurring before I insert the mouse into the usb slot. However the kernel managed to detect one ;) Could you post your /proc/bus/input/devices? On Tuesday 17 July 2007 09:32:49 pm you wrote:
> /proc/bus/input/devices
[lontra@localhost ~]$ cat /proc/bus/input/devices
I: Bus=0017 Vendor=0001 Product=0001 Version=0100
N: Name="Macintosh mouse button emulation"
P: Phys=
S: Sysfs=/class/input/input0
H: Handlers=mouse0 event0
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=3
I: Bus=0011 Vendor=0002 Product=0007 Version=0000
N: Name="SynPS/2 Synaptics TouchPad"
P: Phys=isa0060/serio4/input0
S: Sysfs=/class/input/input1
H: Handlers=mouse1 event1
B: EV=b
B: KEY=6420 0 70000 0 0 0 0 0 0 0 0
B: ABS=11000003
I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/class/input/input2
H: Handlers=kbd event2
B: EV=120013
B: KEY=4 2000000 3802078 f840d001 feffffdf ffefffff ffffffff fffffffe
B: MSC=10
B: LED=7
I: Bus=0003 Vendor=046d Product=c03d Version=0110
N: Name="Logitech USB-PS/2 Optical Mouse"
P: Phys=usb-0000:00:1d.3-1/input0
S: Sysfs=/class/input/input3
H: Handlers=mouse2 event3
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=103
I: Bus=0010 Vendor=001f Product=0001 Version=0100
N: Name="PC Speaker"
P: Phys=isa0061/input0
S: Sysfs=/class/input/input4
H: Handlers=kbd event4
B: EV=40001
B: SND=6
I: Bus=0019 Vendor=0000 Product=0002 Version=0000
N: Name="Power Button (FF)"
P: Phys=button_power/button/input0
S: Sysfs=/class/input/input5
H: Handlers=kbd event5
B: EV=3
B: KEY=100000 0 0 0
I: Bus=0019 Vendor=0000 Product=0005 Version=0000
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/class/input/input6
H: Handlers=event6
B: EV=21
B: SW=1
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button (CM)"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/class/input/input7
H: Handlers=kbd event7
B: EV=3
B: KEY=100000 0 0 0
OK, what about booting with i8042.nomux? Does the box have external PS/2 ports? Hello, I have the same problem on a Lenovo 3000 C200. Here my bug report http://bugs.gentoo.org/show_bug.cgi?id=192314 (with some additional information: dmesg, /proc/bus/input/devices file, emerge --info...) I tried with i8042.nomux=1 (see my dmesg -> http://bugs.gentoo.org/attachment.cgi?id=131233&action=view ) It's seem to be better with "nomux=1" but I still lost sync (see the new dmesg). I don't have any external PS/2 ports. Thank you. I do have the same problem, but I have a differnet hardware (see http://gentoo-wiki.com/HARDWARE_Maxdata_Pro_7000_DX which I am maintaing) In my case I am 99% sure that i8042.nomux=1 is totally working it around; the bug is coupled with this old one http://bugzilla.kernel.org/show_bug.cgi?id=9147 These laptops do have PS2 plugs but they're hard-wired to the keyboard and mouse; theorically, if I would open it I could wire an external keyboard. I have also heard that there are more than the usual 2 PS2 plugs, but I am not sure about this. My feeling is that ACPIPNP is causing the kernel to "eat" some mouse/keyboard IRQs; I am available for further testing. Note: I do have a good amount of C programming experience (for what matters here: sockets, low level hardware, data crunching etc.) but I am relatively new to linux (2 years), and absolutely new to kernel hacking (installed Gentoo on June) - I should be able to understand and try some more technical testcases Created attachment 13128 [details]
legolas558.devices
my /proc/bus/input/devices - note that I have a Synaptics PS/2 Touchpad (integrated)
I do use ipw2100 for the wireless LAN and I can remember the problem did not happen when the module was not loaded (tested only with 2.6.22), e.g. when the wireless adaptor was not ON. I am confirming both the issue and the workaround i8042.nomux=1 on my Acer Travelmate 243LC. This problem is clearly an ACPI issue: the symptoms are shown only if at least one of the following acpi modules is loaded: ac, battery, thermal. If I unload all three of them, my touchpad doesn't lose sync. Daniele, Erik, In comment #2, Chris (the submitter of this bug) noted that the issue at hand does not go away with "acpi=off". By definition, that means this bug report has nothing to do with ACPI. If you have an issue which does go away with "acpi=off", then I invite you to submit a new sighting in the ACPI category, or contribute to an existing one, such as bug #9147. Using acpi=off does nothing. Only i8042.nomux=1 does work around the bug I have managed to track down the cause of my Synaptics touchpad issue. My problem is associated with the orinoco_cs module or a related module. When I use my onboard wireless card using ndiswrapper I do not experience this problem but when I use my Orinoco card which uses the orinoco_cs module I am unable to surf the internet, download, etc. and use my touchpad. This is still present on the 2.6.23 kernel in Fedora too. For me the problem is present for every kernel from 2.6.22 - 2.6.24. I have discovered recently that the problem only exists on the 32-bit x86 architecture, the 64-bit has no such problem. I a this on both 32-bit and 64-bit editions of Fedora and Ubuntu. The current workaround is still i8042.nomux=1, can somebody please confirm this? It didn't resolve the problem completely when I tried on my 2.6.21 kernel (http://bugs.gentoo.org/show_bug.cgi?id=192314#c6). I'm now using a gentoo-sources-2.6.25 and I haven't seen the problem since. However I had some kernel or X freeze (can't remember) but I don't know if it's related to this kernel option. I also saw that someone was complaining for the same problem using Windows XP. On LDLC (french) (I bough mine there as well): Comment title: "Affichage pointeur souris laisse à désirer". Link: http://www.ldlc.com/critiques/PB00047768-1/lenovo-3000-c200-intel-core-2-duo-t5500-512-mo-512-mo-offert-80-go-15-tft-dvd-rw-wi-fi-g-wxph.html Hi all, i've linked the LP #119194 with this bug as it seems these are the same one, https://bugs.launchpad.net/linux/+bug/119194 And with LP bug #34501 https://bugs.launchpad.net/linux/+bug/34501 Thanks again I am not sure if this bug is linked to LP #119194, I have never seen parity errors on my case I have to add that this happens with 2.6.27 on a T400. Setting i8042.nomux=1does _not_ help in my case. Another hint I found somewhere was using i8042.dumbkbd=1, but that did not help here either. I did get some relief, it seems, by setting # echo -n 1 > /sys/devices/platform/i8042/serio1/resetafter Of course, this is just a work-around. I am *NO MORE* using i8042.nomux=1 with kernel 2.6.27-7 (Ubuntu Intrepid Ibex), it seems having been fixed either by activation of nomux through a DMI match or in the kernel source code somewhere. Can somebody please confirm that i8042.nomux=1 is no more necessary to workaround this bug? (In reply to comment #31) The i8042.nomux=1 kernel parameter is still necessary. Perhaps we need a patch... (read on https://bugs.launchpad.net/linux/+bug/119194/comments/34) perhaps acpi_osi=Linux can work around the problem (in place of i8042.nomux=1) This could be a duplicate of #12577, whose fix was just included in the Debian linux kernel. I’ll report here if it works for me with that. Unfortunately not. The patch (http://svn.debian.org/wsvn/kernel/dists/trunk/linux-2.6/debian/patches/features/all/input-alps-add-interleaved-protocol-support.patch?rev=14799&sc=1) only patches alps, but here, on my ThinkPad T400, the synaptics driver grabs the device. Maybe a similar patch for the synaptics driver has to be produced? I can confirm that acpi_osi=Linux resolves the issue on x64 ubuntu 10.04 kernel 2.6.32-22 If changing osi response indeed fixes the issue then ACPI guys will have to take a look here. Hi, all, does the problem still exist in the latest upstream kernel? On $ uname -a Linux kirk 2.6.36-rc6-amd64 #1 SMP Mon Oct 4 09:56:45 UTC 2010 x86_64 GNU/Linux I still observer some issues: [ 52.011328] psmouse.c: TouchPad at isa0060/serio1/input0 lost sync at byte 1 [ 52.011332] psmouse.c: issuing reconnect request [ 217.087051] psmouse.c: TouchPad at isa0060/serio1/input0 lost sync at byte 4 [ 217.087058] psmouse.c: issuing reconnect request [ 287.894903] psmouse.c: TouchPad at isa0060/serio1/input0 lost synchronization, throwing 4 bytes away. [ 288.409026] psmouse.c: resync failed, issuing reconnect request [ 460.823615] psmouse.c: bad data from KBC - timeout [ 460.835107] psmouse.c: TouchPad at isa0060/serio1/input0 lost sync at byte 4 [ 460.835113] psmouse.c: issuing reconnect request [ 466.644117] psmouse.c: Failed to enable mouse on synaptics-pt/serio0 when having both trackpoint and touchpad enabled. It seems the problem occurs less than earlier (but this is just my impression), but it is definitely still present. > this bug did not occur: 2.6.22-1.686
marking as a regression
the problem still exists in the latest upsteam kernel, right? bug closed as there is no response from the bug reporter. please re-open it if the problem still exists in the latest upstream kernel. On 3.2.0, I still have this problem: [ 55.444165] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1 [ 55.446370] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1 [ 55.448494] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1 [ 76.420802] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1 [ 76.423256] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1 [ 76.423258] psmouse serio1: issuing reconnect request But only once since system start so far. I’ll observe it some more... (It seems I lack rights to re-open the bug.) Yes, occurs more often, now also with different text: [ 55.444165] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1 [ 55.446370] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1 [ 55.448494] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1 [ 76.420802] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1 [ 76.423256] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1 [ 76.423258] psmouse serio1: issuing reconnect request [ 389.906979] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1 [ 389.909379] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1 [ 389.911666] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1 [ 389.943244] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1 [ 389.945504] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1 [ 389.945507] psmouse serio1: issuing reconnect request [ 650.377282] psmouse serio1: TouchPad at isa0060/serio1/input0 lost synchronization, throwing 5 bytes away. [ 650.888206] psmouse serio1: resync failed, issuing reconnect request I have same trouble. Notebook Samsung 350u2b. Archlinux. Sometimes touchpad not workinkg. That happens when one finger in the lower right corner, and the other finger on the center of the touchpad. $ xinput list | grep Touchpad ⎜ ↳ ETPS/2 Elantech Touchpad id=12 [slave pointer (2)] $dmesg [ 4335.879836] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at byte 6 [ 4335.908340] psmouse serio1: Touchpad at isa0060/serio1/input0 - driver resynced. [ 5018.411486] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at byte 6 [ 5018.423943] psmouse serio1: Touchpad at isa0060/serio1/input0 - driver resynced. [ 5029.876019] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at byte 6 [ 5029.897982] psmouse serio1: Touchpad at isa0060/serio1/input0 - driver resynced. Solution, Just reload psmouse module. $rmmod psmouse $modprobe psmouse Kernel: $uname -a Linux samsung 3.5.4-1-ARCH #1 SMP PREEMPT Sat Sep 15 08:12:04 CEST 2012 x86_64 GNU/Linux (In reply to comment #45) > I have same trouble. Notebook Samsung 350u2b. Archlinux. > > Sometimes touchpad not workinkg. > > That happens when one finger in the lower right corner, and the other finger > on > the center of the touchpad. > > > $ xinput list | grep Touchpad > ⎜ ↳ ETPS/2 Elantech Touchpad id=12 [slave pointer (2)] This is not Synaptics but Elantech touchpad. Could you please open a separate bug report for this? I'm moving this bug from acpi to drivers/input-dev, please correct me if this is not the right component, thanks. I have the same problem on kernel 3.8.3. I found this patch: http://thread.gmane.org/gmane.linux.kernel.input/25599 And it solves the problem. Why it still isn't merged? The patch from comment #48 also fixes the problem for me. Would be nice to see if it can be merged. This is my Touchpad model: psmouse serio1: synaptics: Touchpad model: 1, fw: 7.4, id: 0x1e0b1, caps: 0xd04773/0xe40000/0x5a0400, board id: 3655, fw id: 684465 Since 3.9 this extremely bugs me. <3.9 only needed some seconds to get my psmouse up, but since 3.9 I get hangs during usage, may happen several times per minute - quite unusable :( Even worse it sometimes does not recover automatically and makes the whole keyboard unusable - no ctrl+alt+backspace, no shortcuts to fire up e17-everything. I need to sleep + resume my Laptop to get it working again. The first time this happened I thought I had a kernel deadlock. Good luck I just tried to get it Suspended before hard powering off... The weird thing: I did not enable TouchPad in the kernel, I did not install synaptics xorg-driver. I only use the TrackPoint from my Lenovo L520. The touchpad can't be enabled, it's "dead". But I get these errors: [198183.044677] psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at byte 4 [198183.056488] psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at byte 4 [198183.057870] psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at byte 1 [198183.059166] psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at byte 1 [198183.060198] psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at byte 1 [198183.060205] psmouse serio4: issuing reconnect request [198821.998906] psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at byte 4 [198822.000232] psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at byte 1 [198822.019445] psmouse serio4: TouchPad at isa0060/serio4/input0 - driver resynced. If you think this is another issue I will open a new bug report. I just merged Eric's patch and it should be in 3.10, however if there was a significant regression in 3.9 compared to 3.8 that would mean there is another issue, probably outside of the input subsystem. I wonder if you will be to try bisecting this regression. I also had issues with my touchpad [1] in 3.8. Therefore I tested 3.10rc7 to if the patch brought improvement. I must admit compared to 3.8 it's definitely an improvement although the issue is not fixed completely. I still get the dmesg output [2] and I still get an unusable touchpad during heavily typing (just typing a lot a move the touchpad to reproduce). But in comparison to 3.8 it only takes 2 seconds until the touchpad works again (you just need to stop typing). The is also this patch from google [3]. Anyone tried it yet ? [1] psmouse serio4: synaptics: Touchpad model: 1, fw: 7.2, id: 0x1c0b1, caps: 0xd047b3/0xb40000/0xa0000, board id: 71, fw id: 578367 [2] smouse serio4: issuing reconnect request [ 176.650713] psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at byte 4 [ 176.652089] psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at byte 1 [ 176.670212] psmouse serio4: TouchPad at isa0060/serio4/input0 - driver resynced. [ 179.109667] psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at byte 4 [ 179.118082] psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at byte 4 [ 179.119450] psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at byte 1 [ 179.124539] psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at byte 1 [ 179.140162] psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at byte 4 [ 179.140175] psmouse serio4: issuing reconnect request [3] https://patchwork.kernel.org/patch/2156601/ Tested Chromium's patch [1] on Kernel 3.8, with no improvement here. [1] https://patchwork.kernel.org/patch/2156601/ Just a small update. I still have this issues in 3.11-rc2 on Lenovo L520. If you need an xev.log or similar, please have a look at Ubuntu's bugreport [1], where I recently filed all these. [1] https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/896922 ThinkPad-L520 with 3.2.0-53-generic and *still* and issue. Since 3.2.0-45 I have this problem and I have no idea how to fix it. I tried many things and none works. I have a new Thinkpad t440s which has this issue, where the touchpad loses sync every few minutes, sometimes resyncing successfully, sometimes locking up and requiring a modprobe psmouse to get going again. This happens with 3.11 and the latest kernel mainline 3.13.1-031301 This is being tracked under the ubuntu tracker here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268365 If you need any information, want anything tested, or if there is anything I can do to help fix this then please let me know. Given that the other bug is closed per hardware fail, this one can be closed too. For reference: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268365/comments/14 I am seeing this issue with a Latitude E7440 on Arch Linux with the default 3.16.4 kernel. dmesg output related to this bug (systemd): [ 6135.425681] psmouse serio1: GlidePoint at isa0060/serio1/input0 lost sync at byte 1 [ 6135.426716] psmouse serio1: GlidePoint at isa0060/serio1/input0 lost sync at byte 1 [ 6135.427730] psmouse serio1: GlidePoint at isa0060/serio1/input0 lost sync at byte 1 [ 6135.430819] psmouse serio1: GlidePoint at isa0060/serio1/input0 - driver resynced. [ 6943.621660] psmouse serio1: GlidePoint at isa0060/serio1/input0 lost sync at byte 1 [ 6943.624732] psmouse serio1: GlidePoint at isa0060/serio1/input0 - driver resynced. [ 6943.625690] psmouse serio1: GlidePoint at isa0060/serio1/input0 lost sync at byte 1 [ 6943.632644] psmouse serio1: GlidePoint at isa0060/serio1/input0 - driver resynced. [ 6943.633638] psmouse serio1: GlidePoint at isa0060/serio1/input0 lost sync at byte 1 [ 6943.636722] psmouse serio1: GlidePoint at isa0060/serio1/input0 - driver resynced. uname -a: Linux george 3.16.4-1-ARCH #1 SMP PREEMPT Mon Oct 6 08:22:27 CEST 2014 x86_64 GNU/Linux Relevant dmidecode info: Handle 0x0004, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J1A1 Internal Connector Type: None External Reference Designator: PS2Mouse External Connector Type: PS/2 Port Type: Mouse Port Handle 0x0026, DMI type 21, 7 bytes Built-in Pointing Device Type: Touch Pad Interface: Bus Mouse Buttons: 2 Relevant lsmod info: i8042 18002 2 libps2,dell_laptop serio 18282 6 serio_raw,atkbd,i8042,psmouse I recently bought an ASUS X553M laptop and have run into this problem. A few observations I would like to share: I downloaded and installed the live Fc20 version of Fedora. It came with a kernel version of 3.11.10-301.fc20.x86_64. The touchpad was working as a mouse - allowing cursor positioning and tapping. After installation the broadcom 4312 14e4:4365 wifi interface was not recognized so applied the process mentioned in the broadcomm site for this adapter. The kernel version changed to 3.16.6-203.chitrai.fc20.x86_64. Wifi worked like a charm. But the touchpad stopped working. However the touchpad now is being recognised as an ELantech touchpad and synclient shows a lot of properties of the device. Working on the touchpad leads to the "psmouse serio4: Touchpad at isa0060/serio4/input0 lost sync at byte 6" messages for every position. I also notice that after the wifi driver was installed and kernel changed #rmmod psmouse gives the following message rmmod: ERROR: Module psmouse is builtin. I did a simple custom compilation to see if compiling on the required hardware platform will fix the issue. It didn't. I have not tried the patch. Hope this helps. The kernel version changed to 3.16.6-203.fc20.x86_64 after the wifi driver fix. 3.16.6-203.chitrai.fc20.x86_64 was the vanilla compile. Apologies for the oversight in typing. |