linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Bruin <jmdebruin@xmsnet.nl>
To: Hans de Goede <hdegoede@redhat.com>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input <linux-input@vger.kernel.org>,
	"linux-kernel@vger.kernel.org >> Linux Kernel Mailing List"
	<linux-kernel@vger.kernel.org>,
	"Pali Rohár" <pali.rohar@gmail.com>
Subject: Re: 4.0.0-rc mouse/keyboard events get stuck
Date: Wed, 08 Apr 2015 21:06:20 +0200	[thread overview]
Message-ID: <55257C2C.1010205@xmsnet.nl> (raw)
In-Reply-To: <55254969.5060402@redhat.com>

On 04/08/2015 05:29 PM, Hans de Goede wrote:
> Hi,
>
> On 08-04-15 12:59, Hans de Bruin wrote:
>> On 04/06/2015 11:23 PM, Dmitry Torokhov wrote:
>>> Hi Hans,
>>>
>>> On Mon, Apr 6, 2015 at 11:39 AM, Hans de Bruin <jmdebruin@xmsnet.nl>
>>> wrote:
>>>> Since 4.0.0-rc something mu laptop has some mouse /keyboard problems.
>>>> When I play KDE kpatience, a card game, card stick to my
>>>> mousepointer: left
>>>> mouse button down on a card, move mouse pointer and card to another
>>>> place.
>>>> left mouse button up to drop the card. This should drop the card,
>>>> but often
>>>> the mouse button up events gets stuck somewhere until I move he mouse
>>>> pointer a little bit.
>>>> In web based mail clients something similar happens when I drag mail to
>>>> another folder.
>>>> Sometime after I start a xterm and start typing, the letters don't
>>>> appear
>>>> until move the mouse pointer.
>>>>
>>>> Bisecting is out of the question. This kernel realease was so
>>>> dramatic I was
>>>> glad to have functioning kde screen when rc4 arrived.
>>>>
>>>> My laptop is a Dell Latitude D430, it has a touchpad and a pointer
>>>> an two
>>>> sets of buttons.
>>>>
>>>> dmesg
>>>> [    0.636492] input: AT Translated Set 2 keyboard as
>>>> /devices/platform/i8042/serio0/input/input4
>>>> [    0.633108] mousedev: PS/2 mouse device common for all mice
>>>> [   80.543044] input: PS/2 ALPS Mouse as
>>>> /devices/platform/i8042/serio1/input/input8
>>>
>>> Linus just merged 2 fixes to ALPS driver that might help you. Could
>>> you please try compiling tip of the tree and telling me if it fixes
>>> your issue?
>>>
>>
>> I am at rc.7 and the problem is still there. But maybe you can get
>> away with "user error". Here is a picture of the layout of my laptop:
>>
>> http://img.clubic.com/000000DC00604500-photo-dell-latitude-d430-4.jpg
>>
>> Lets call the blue thing ts. The buttons directly beneath the keys
>> ts-l and ts-r. For the touchpad tp, tp-l and tp-r. And because one can
>> never have to many input devices um, um-l and um-r for a usb mouse.
>>
>> When I play kpatience and stick to one device ts or ts-l or mp and
>> mp-l no problems arise. I can also mix devices for example um and
>> tp-l. There are several combinations. Only one of these ts and tp-l
>> show the problematic behavior. This is the way i use my laptop (user
>> error?)
>
> Ok, this one is a regression which is caused by:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/input/mouse/alps.c?id=04aae283ba6a8cd4851d937bf9c6d6ef0361d794
>
>
> I've attached a fix which I will formally send / submit upstream in a
> few minutes too.
>

This patch fixes the regression on my laptop. Thanks for the quick response.

-- 
Hans


  reply	other threads:[~2015-04-08 19:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-06 18:39 4.0.0-rc mouse/keyboard events get stuck Hans de Bruin
2015-04-06 21:23 ` Dmitry Torokhov
2015-04-08 10:59   ` Hans de Bruin
2015-04-08 11:46     ` Hans de Goede
2015-04-08 15:29     ` Hans de Goede
2015-04-08 19:06       ` Hans de Bruin [this message]
2015-04-08 16:04     ` Hans de Goede
2015-04-08 19:07       ` Hans de Bruin

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=55257C2C.1010205@xmsnet.nl \
    --to=jmdebruin@xmsnet.nl \
    --cc=dmitry.torokhov@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pali.rohar@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).