Bug 750511

Summary: TouchPad from time to time does not react
Product: [Fedora] Fedora Reporter: Dirk Foerster <dirk.foerster>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-28 13:53:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Dirk Foerster 2011-11-01 12:55:40 UTC
Description of problem:
TouchPad from time to time does not react to movements. Also missing is single and double click functionality when tipping with finger on TouchPad area. That only works with TouchPad's left key but not when tipping on the TouchPad area.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Nov  1 14:29:53 formula007 kernel: [  221.554572] psmouse.c: TouchPad at isa0060/serio2/input0 lost sync at byte 4
Nov  1 14:29:53 formula007 kernel: [  221.557879] psmouse.c: TouchPad at isa0060/serio2/input0 lost sync at byte 1
Nov  1 14:29:53 formula007 kernel: [  221.573829] psmouse.c: TouchPad at isa0060/serio2/input0 - driver resynched.
Nov  1 14:35:22 formula007 kernel: [  550.593574] psmouse.c: TouchPad at isa0060/serio2/input0 lost sync at byte 4
Nov  1 14:35:22 formula007 kernel: [  550.595284] psmouse.c: TouchPad at isa0060/serio2/input0 lost sync at byte 1
Nov  1 14:35:22 formula007 kernel: [  550.610391] psmouse.c: TouchPad at isa0060/serio2/input0 - driver resynched.

Comment 1 Josh Boyer 2012-06-07 15:08:03 UTC
Is this still an issue on 2.6.43/3.3?

Comment 2 Dirk Foerster 2012-06-10 11:00:49 UTC
(In reply to comment #1)
> Is this still an issue on 2.6.43/3.3?

Yes, problem persists.

System now is:
3.3.7-1.fc16.x86_64
GNOME 3.2.1

Message:
Jun 10 12:53:51 formula007 kernel: [ 1174.853453] psmouse serio2: TouchPad at isa0060/serio2/input0 lost sync at byte 1
Jun 10 12:53:51 formula007 kernel: [ 1174.856670] psmouse serio2: TouchPad at isa0060/serio2/input0 lost sync at byte 1
Jun 10 12:53:51 formula007 kernel: [ 1174.858427] psmouse serio2: TouchPad at isa0060/serio2/input0 lost sync at byte 1
Jun 10 12:53:51 formula007 kernel: [ 1174.861577] psmouse serio2: TouchPad at isa0060/serio2/input0 lost sync at byte 1
Jun 10 12:53:51 formula007 kernel: [ 1174.863317] psmouse serio2: TouchPad at isa0060/serio2/input0 lost sync at byte 1
Jun 10 12:53:51 formula007 kernel: [ 1174.863321] psmouse serio2: issuing reconnect request

Jun 10 12:58:12 formula007 kernel: [ 1435.893075] psmouse serio2: TouchPad at isa0060/serio2/input0 lost sync at byte 4
Jun 10 12:58:12 formula007 kernel: [ 1435.896358] psmouse serio2: TouchPad at isa0060/serio2/input0 lost sync at byte 1
Jun 10 12:58:12 formula007 kernel: [ 1435.911325] psmouse serio2: TouchPad at isa0060/serio2/input0 - driver resynced.

Comment 3 Dave Jones 2012-10-23 15:36:38 UTC
# Mass update to all open bugs.

Kernel 3.6.2-1.fc16 has just been pushed to updates.
This update is a significant rebase from the previous version.

Please retest with this kernel, and let us know if your problem has been fixed.

In the event that you have upgraded to a newer release and the bug you reported
is still present, please change the version field to the newest release you have
encountered the issue with.  Before doing so, please ensure you are testing the
latest kernel update in that release and attach any new and relevant information
you may have gathered.

If you are not the original bug reporter and you still experience this bug,
please file a new report, as it is possible that you may be seeing a
different problem. 
(Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).

Comment 4 Dirk Foerster 2012-10-26 19:01:13 UTC
Using kernel 3.6.2-4.fc17.x86_64. Problem persists.

Comment 5 Josh Boyer 2013-03-14 17:38:41 UTC
Are you still having issues with 3.8.2 in updates-testing?

Comment 6 Josh Boyer 2013-03-28 13:53:18 UTC
This bug is being closed with INSUFFICIENT_DATA as there has not been a
response in 2 weeks.  If you are still experiencing this issue,
please reopen and attach the relevant data from the latest kernel you are
running and any data that might have been requested previously.