linux-kernel - [BISECTED] Re: psmouse.c: GlidePoint at isa0060/serio1/input0 lost sync at byte 1

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 7 Jan 2008 21:24:58 +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>,
	"William Pettersson" <william.pettersson@...il.com>
Subject: [BISECTED] Re: psmouse.c: GlidePoint at isa0060/serio1/input0 lost sync at byte 1

Hi,

On Nov 14, 2007 9:26 PM, Vegard Nossum <vegard.nossum@...il.com> wrote:
> 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?

I have now bisected the kernel (to the point where I made a guess) and
found that reverting this commit fixes my problem:

commit dac4ae0daa1be36ab015973ed9e9dc04a2684395
Author: William Pettersson <william.pettersson@...il.com>
Date:   Wed Sep 5 00:18:44 2007 -0400

    Input: ALPS - add support for model found in Dell Vostro 1400

    Signed-off-by: William Pettersson <william.pettersson@...il.com>
    Signed-off-by: Dmitry Torokhov <dtor@...l.ru>

diff --git a/drivers/input/mouse/alps.c b/drivers/input/mouse/alps.c
index 2c5f11a..a810ff8 100644 (file)
--- a/drivers/input/mouse/alps.c
+++ b/drivers/input/mouse/alps.c
@@ -53,6 +53,7 @@ static const struct alps_model_info alps_model_data[] = {
        { { 0x20, 0x02, 0x0e }, 0xf8, 0xf8, ALPS_PASS | ALPS_DUALPOINT
}, /* XXX */
        { { 0x22, 0x02, 0x0a }, 0xf8, 0xf8, ALPS_PASS | ALPS_DUALPOINT },
        { { 0x22, 0x02, 0x14 }, 0xff, 0xff, ALPS_PASS | ALPS_DUALPOINT
}, /* Dell Latitude D600 */
+       { { 0x73, 0x02, 0x50 }, 0xcf, 0xff, ALPS_FW_BK_1 } /* Dell
Vostro 1400 */
 };


After reverting, all buttons work as expected -- no lost syncs. I
might add that my laptop is Acer Aspire 5720ZG. Also, the button in
question is not truly a middle button; when operating correctly, it is
used for scrolling (up/down). Now what can be done to make both models
work correctly?


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/