lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <19f34abd0711141226n60323630rdc4833db0bfb2eeb@mail.gmail.com>
Date:	Wed, 14 Nov 2007 21:26:01 +0100
From:	"Vegard Nossum" <vegard.nossum@...il.com>
To:	"Dmitry Torokhov" <dmitry.torokhov@...il.com>,
	linux-input@...r.kernel.org,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: psmouse.c: GlidePoint at isa0060/serio1/input0 lost sync at byte 1

Hello,

With 2.6.23 kernel, the laptop middle button worked fine. With
2.6.24-rc1, when I press the middle button, the cursor jumps around
the screen and this appears in the kernel log (for each time I press
the button):

psmouse.c: GlidePoint at isa0060/serio1/input0 lost sync at byte 1
psmouse.c: GlidePoint at isa0060/serio1/input0 lost sync at byte 1
psmouse.c: GlidePoint at isa0060/serio1/input0 - driver resynched.

Related dmesg:

input: Macintosh mouse button emulation as /class/input/input0
PNP: PS/2 Controller [PNP0303:KBC0,PNP0f13:MSE0] at 0x60,0x64 irq 1,12
mice: PS/2 mouse device common for all mice
input: PS/2 Mouse as /class/input/input2
input: AlpsPS/2 ALPS GlidePoint as /class/input/input3

Earlier dmesgs (2.6.23) had (only) this:

input: Macintosh mouse button emulation as /class/input/input0
PNP: PS/2 Controller [PNP0303:KBC0,PNP0f13:MSE0] at 0x60,0x64 irq 1,12
mice: PS/2 mouse device common for all mice
input: ImPS/2 Generic Wheel Mouse as /class/input/input2


It seems that the driver used is different. What can I do to fix this?


Kind regards,
Vegard Nossum
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ