From: Marc Koschewski <marc@osknowledge.org>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: Marc Koschewski <marc@osknowledge.org>,
linux-kernel@vger.kernel.org, 340202@bugs.debian.org
Subject: psmouse unusable in -mm series (was: 2.6.15-rc1-mm2 unsusable on DELL Inspiron 8200, 2.6.15-rc1 works fine)
Date: Wed, 23 Nov 2005 20:57:02 +0100 [thread overview]
Message-ID: <20051123195700.GB7446@stiffy.osknowledge.org> (raw)
In-Reply-To: <200511212243.50707.dtor_core@ameritech.net>
* Dmitry Torokhov <dtor_core@ameritech.net> [2005-11-21 22:43:50 -0500]:
> On Sunday 20 November 2005 12:14, Marc Koschewski wrote:
> > * Dmitry Torokhov <dtor_core@ameritech.net> [2005-11-18 22:07:19 -0500]:
> >
> > > On Friday 18 November 2005 13:29, Marc Koschewski wrote:
> > > > Nov 18 12:58:37 stiffy kernel: psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away.
> > > >
> > > > SOME STUFF MISSING? HUH?
> > > >
> > > > Nov 18 13:03:14 stiffy kernel: psmouse.c: resync failed, issuing reconnect request
> > > >
> > >
> > > Hm, this worries me a bit... Could you please try appying the patch
> > > below to plain 2.6.15-rc1 and see if mouse starts misbehaving again?
> >
> > Dmitry,
> >
> > I applied the 5 patches to a plain 2.6.15-rc1. The mouse was well as if it was
> > in an unpatched kernel. The problem just occured in 2.6.15-rc1-mmX.
> > Plain 2.6.15-rc1 was fine before as well. So: actually no change.
> >
> > Need any more info?
> >
>
> Marc,
>
> Thank you for testing the patch. It proves that your mouse troubles
> were not caused by the patch I made so I am very happy. "No change"
> is the result I wanted to hear ;)
>
Dmitry,
there's a bug report filed against Debian's udev. You can read it here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=340202
The bug report, however, states that the problem is caused by udev under
all variants of kernel 2.6.15. I'm writing this mail while running
2.6.15-rc1 and the mouse definitely works. Do you have any other hint?
Seems to me like the bug report is only half the truth...
Regards,
Marc
next prev parent reply other threads:[~2005-11-23 19:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 18:29 2.6.15-rc1-mm2 unsusable on DELL Inspiron 8200, 2.6.15-rc1 works fine Marc Koschewski
2005-11-18 19:28 ` Hugh Dickins
2005-11-19 0:31 ` Marc Koschewski
2005-11-19 3:07 ` Dmitry Torokhov
2005-11-20 17:14 ` Marc Koschewski
2005-11-22 3:43 ` Dmitry Torokhov
2005-11-22 10:14 ` Marc Koschewski
2005-11-23 19:57 ` Marc Koschewski [this message]
2005-11-24 2:29 ` psmouse unusable in -mm series (was: 2.6.15-rc1-mm2 unsusable on DELL Inspiron 8200, 2.6.15-rc1 works fine) Ed Tomlinson
2005-11-24 4:41 ` Dmitry Torokhov
2005-11-24 8:41 ` Marc Koschewski
2005-11-24 12:17 ` Ed Tomlinson
2005-11-24 12:44 ` Marc Koschewski
2005-11-24 20:23 ` Rafael J. Wysocki
2005-11-24 21:20 ` Rafael J. Wysocki
2005-11-25 8:22 ` Vojtech Pavlik
2005-11-25 13:50 ` Marc Koschewski
2005-11-25 21:16 ` Rafael J. Wysocki
2005-11-25 21:41 ` Dmitry Torokhov
2005-11-26 3:54 ` Dmitry Torokhov
2005-11-26 4:50 ` Dmitry Torokhov
2005-11-26 17:28 ` Rafael J. Wysocki
2005-11-28 6:01 ` Dmitry Torokhov
2005-11-25 13:53 ` Marc Koschewski
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=20051123195700.GB7446@stiffy.osknowledge.org \
--to=marc@osknowledge.org \
--cc=340202@bugs.debian.org \
--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
all inboxes | Powered by JetHome®