kernel-packages team mailing list archive

[Allan Crooks <allan@xxxxxxxxxx>]

There was some discussion about this bug on the linux.kernel.input group
a few months ago - see the link in comment #47.

There was an e-mail I did receive from Tommy Will which I thought was
also posted to the newsgroup, but apparently not, so I'm going to
include it here:

----

Sorry for wait a long time. I investigated this issue and with my
"Dell Latitude D630 + Dock + External Rushmore device" environment,
I can reproduce it with a very low rate.

"psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync
at byte 6" occurred after I continuously touch the
 touchpad for more than 5 minutes.
However, it seems a bit difference from yours. Once my touchpad lost
sync, it will recover immediately and will not occur
until next 5 minutes. (From your mail, it seems much easier to reproduce)

After that, I tried to investigate with my low reproduce rate
environment. Here is what I have tried.

1) Log the raw data and locate why "lost sync" occurred.
    I found that when "lost sync" occurred, it first received several
unknown packet that could not pass our packet valid logic. I asked
our H/W team member to check if it maybe our device's potential bug or
a hidden mode, but got the answer with "NO". Our F/W did not ever
design such packet format and they never saw that. (Please see my
attached picture)

2) In order to know where such weird packet comes, I used a tool to
capture the raw PS/2 data sent from touchpad. However, as long as
I connect the tool to debug, I can not reproduce the issue anymore : (
# I'm not familiar with H/W and have no idea why...
So, in a word, I still can not prove that this weird packet does not
come from our touchpad.

And here is my guess.
In laptop, there is a module called "EC". It's main for coordinate the
PS/2 data for both touchpad & keyboard. I'm now wondering if it's a
potential issue
of Linux EC driver for E7440. Under some situation, maybe EC will
forward wrong data to our input driver ?
If so, that will be help to explain why I can almost not reproduce it
on my side.

Finally, when I investigate this issue, I found some initialization
are no longer needed in latest Windows driver. Although I do not think
it's the root cause
of this time's issue, if it's lucky enough, it may have chance to
reduce the reproduce rate. Please have a try if you have time

----

On a sidenote, this problem seems to be worse on Ubuntu 14.04.

** Attachment added: "Attachment given with quoted email"
   https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258837/+attachment/4131533/+files/LostSyncLog.png

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1258837

Title:
  [Dell Latitude E7440] ALPS touchpad keeps having state reset

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  The mouse cursor keeps on jumping around, and these messages appear in the log when it happens:
  Dec  7 21:57:26 wyvern kernel: [  648.133841] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1
  Dec  7 21:57:26 wyvern kernel: [  648.134868] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1
  Dec  7 21:57:26 wyvern kernel: [  648.137921] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced.
  Dec  7 21:57:26 wyvern kernel: [  648.138852] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1
  Dec  7 21:57:26 wyvern kernel: [  648.148833] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced.

  The touchpad is recognised as a "AlpsPS/2 ALPS DualPoint TouchPad".
  This is occurring with Ubuntu 13.10, though I have also seen this
  behaviour in the version of Linux Mint based on Ubuntu 13.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-14-generic 3.11.0-14.21
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Uname: Linux 3.11.0-14-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC1:  allanc     1852 F.... pulseaudio
   /dev/snd/controlC0:  allanc     1852 F.... pulseaudio
  Date: Sat Dec  7 22:19:22 2013
  HibernationDevice: RESUME=UUID=a2a36712-35de-4e20-9d1a-df3520f401ec
  InstallationDate: Installed on 2013-12-07 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
  MachineType: Dell Inc. Latitude E7440
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic.efi.signed root=UUID=d03a42e6-0dea-4969-a682-eb4d255abc70 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-14-generic N/A
   linux-backports-modules-3.11.0-14-generic  N/A
   linux-firmware                             1.116
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 07F3F4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/14/2013:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn07F3F4:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258837/+subscriptions