public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* [RFC/RFT 0/5] Input locking patches
@ 2007-07-24  4:45 Dmitry Torokhov
  2007-07-24  4:45 ` [RFC/RFT 1/5] Input: implement proper locking in input core Dmitry Torokhov
                   ` (5 more replies)
  0 siblings, 6 replies; 15+ messages in thread
From: Dmitry Torokhov @ 2007-07-24  4:45 UTC (permalink / raw)
  To: linux-input; +Cc: linux-kernel

Hi everyone,

I finally managed to put together some patches implementing
locking in input core and main input handles. Please look
over them and give them a spin.

--
Dmitry

^ permalink raw reply	[flat|nested] 15+ messages in thread
* Re: [RFC/RFT 0/5] Input locking patches
@ 2007-07-28  4:41 Al Boldi
  0 siblings, 0 replies; 15+ messages in thread
From: Al Boldi @ 2007-07-28  4:41 UTC (permalink / raw)
  To: linux-kernel

Indan Zupancic wrote:
> On Tue, July 24, 2007 06:45, Dmitry Torokhov wrote:
> > Hi everyone,
> >
> > I finally managed to put together some patches implementing
> > locking in input core and main input handles. Please look
> > over them and give them a spin.
>
> Since kernel 2.6.21 or so I was annoyed by a warping mouse, and
> one kernel version later also by "stuck" keys, causing repeated input
> at the most inconvenient moments (e.g. when opening a program by
> pressing F1).
>
> As it happened irregularly and unpredictable it was hard to debug,
> and I suspected faulty hardware. My cpu was quite hot, but after
> removing all the dust it seems all right again. Unfortunately that
> was about the same time I upgraded to 2.6.23-rc1, so all I can say
> is that the stuck key problem seems to be gone, though not sure
> thanks to what, but that neither the cleaning nor the upgrade fixed
> the warping mouse problem.
>
> I'm running with these locking patches for two days now and the
> mouse doesn't warp any more (it can also have fixed the stuck key
> problem, not sure). Normally it would warp several times a day,
> and that didn't happen yet, so I'm tempted to praise your patches.
>
> Sorry for the babbling, just wanted to say that I've tested these
> patches and that they seem to fix real problems.

Thanks for babbling!

I'm having these same intermittent problems starting around 2.6.21, and 
wasn't really sure if it was hardware or not, so didn't bother reporting 
them.  This is what I see sometimes in the logs:

=====================================
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
input: PC Speaker as /class/input/input3
input: AT Translated Set 2 keyboard as /class/input/input4
input: ImPS/2 Generic Wheel Mouse as /class/input/input5
psmouse.c: bad data from KBC - bad parity
psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, 
throwing 2 bytes away.
=====================================

Thanks!

--
Al
 

^ permalink raw reply	[flat|nested] 15+ messages in thread

end of thread, other threads:[~2007-07-29 12:50 UTC | newest]

Thread overview: 15+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-07-24  4:45 [RFC/RFT 0/5] Input locking patches Dmitry Torokhov
2007-07-24  4:45 ` [RFC/RFT 1/5] Input: implement proper locking in input core Dmitry Torokhov
2007-07-24  5:35   ` Jeff Garzik
2007-07-24  5:52     ` Dmitry Torokhov
2007-07-27 23:28   ` Indan Zupancic
2007-07-29  3:50     ` Dmitry Torokhov
2007-07-29 12:50       ` Indan Zupancic
2007-07-24  4:45 ` [RFC/RFT 2/5] evdev - implement proper locking Dmitry Torokhov
2007-07-24  4:45 ` [RFC/RFT 3/5] Input: tsdev " Dmitry Torokhov
2007-07-24  4:45 ` [RFC/RFT 4/5] Input: mousedev " Dmitry Torokhov
2007-07-24  4:45 ` [RFC/RFT 5/5] Input: joydev " Dmitry Torokhov
2007-07-27 22:25 ` [RFC/RFT 0/5] Input locking patches Indan Zupancic
2007-07-29  3:38   ` Dmitry Torokhov
2007-07-29 12:15     ` Indan Zupancic
  -- strict thread matches above, loose matches on Subject: below --
2007-07-28  4:41 Al Boldi

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox