public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Victor Hahn <victorhahn@web.de>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Really annoying bug in the mouse driver
Date: Tue, 01 Feb 2005 09:54:37 +0100	[thread overview]
Message-ID: <41FF43CD.7080901@web.de> (raw)
In-Reply-To: <200501280206.06747.dtor_core@ameritech.net>

Hi Dmitry,

thank you for the patch! Unfortunately, I wasn't able to apply it 
correctly, neither to kernel 2.6.10 nor to kernel 2.6.4. Here's the 
error message I got:

root@vic:/mnt/hdb3/Installationsdateien/SOURCES/linux-2.6.10# patch -p1 
< /home/victor/patch-mouse.diff
patching file drivers/input/mouse/psmouse-base.c
Hunk #1 FAILED at 154.
Hunk #2 succeeded at 220 (offset 37 lines).
1 out of 2 hunks FAILED -- saving rejects to file 
drivers/input/mouse/psmouse-base.c.rej
patching file drivers/input/mouse/psmouse.h
Hunk #1 succeeded at 11 (offset -2 lines).
Hunk #2 succeeded at 50 with fuzz 1 (offset 4 lines).

And here's the contents of drivers/input/mouse/psmouse-base.c.rej (same 
in both kernel versions):

***************
*** 154,162 ****
                                flags & SERIO_TIMEOUT ? " timeout" : "",
                                flags & SERIO_PARITY ? " bad parity" : "");
                ps2_cmd_aborted(&psmouse->ps2dev);
                goto out;
        }

        if (unlikely(psmouse->ps2dev.flags & PS2_FLAG_ACK))
                if  (ps2_handle_ack(&psmouse->ps2dev, data))
                        goto out;
--- 154,172 ----
                                flags & SERIO_TIMEOUT ? " timeout" : "",
                                flags & SERIO_PARITY ? " bad parity" : "");
                ps2_cmd_aborted(&psmouse->ps2dev);
+               if (psmouse->resend || serio_write(serio, 
PSMOUSE_CMD_RESEND)) {
+                       psmouse->resend = 0;
+                       psmouse->state = PSMOUSE_IGNORE;
+                       serio_reconnect(serio);
+               } else {
+                       psmouse->pktcnt = 0;
+                       psmouse->resend = 1;
+               }
                goto out;
        }

+       psmouse->resend = 0;
+
        if (unlikely(psmouse->ps2dev.flags & PS2_FLAG_ACK))
                if  (ps2_handle_ack(&psmouse->ps2dev, data))
                        goto out;

I compiled the kernel (2.6.10) like this anyway but this made it even 
worse: The problem still did occur, but it didn't go away any more, 
neither by waiting nor by moving the mouse nor by switching to a 
console. I still get the same error message as before, but this is now 
additionally printed to tty1.

It would be great if you could help me with this.

Regards,
Victor



Dmitry Torokhov wrote:

>On Saturday 15 January 2005 08:16, Victor Hahn wrote:
>  
>
>>Jan 15 13:33:36 vic kernel: psmouse.c: bad data from KBC - bad parity
>>Jan 15 13:33:38 vic kernel: psmouse.c: Wheel Mouse at 
>>isa0060/serio1/input0 lost
>> synchronization, throwing 3 bytes away.
>>
>>Sometimes, only one of these messages appears; the number of bytes in 
>>the second message varies, but mostly it is 3.
>>
>>    
>>
>
>Hi,
>
>Could you please try the patch below?
>
>Thanks!
>
>  
>


  reply	other threads:[~2005-02-01  8:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-15 13:16 Really annoying bug in the mouse driver Victor Hahn
2005-01-28  7:06 ` Dmitry Torokhov
2005-02-01  8:54   ` Victor Hahn [this message]
2005-02-01 13:56     ` Dmitry Torokhov
2005-02-01 14:19       ` Victor Hahn
2005-02-01 23:19         ` Dmitry Torokhov
2005-02-02  6:08           ` Victor Hahn
2005-02-02  6:26             ` Dmitry Torokhov
2005-02-02 10:22               ` Victor Hahn
2005-02-02 15:44                 ` Dmitry Torokhov
2005-02-03 15:05                   ` Victor Hahn
2005-02-03 15:17                     ` Dmitry Torokhov
2005-02-01 13:29   ` zhilla

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=41FF43CD.7080901@web.de \
    --to=victorhahn@web.de \
    --cc=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox