LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
* keyboard + PS/2 mouse locks after opening psaux
@ 2001-10-09 10:21 Krzysztof Halasa
  2001-10-11 15:24 ` Marius Gedminas
  2001-12-16  1:36 ` Krzysztof Halasa
  0 siblings, 2 replies; 5+ messages in thread
From: Krzysztof Halasa @ 2001-10-09 10:21 UTC (permalink / raw)
  To: linux-kernel

Hi,

I'm having the following problem: after I start X11 (or gpm with no X)
my keyboard and PS/2 mouse sometimes locks up. What could that be?

440BX UP celeron mobo here (Abit - BH6?), '94 AT keyboard, '2000 A4tech
2-wheel mouse, various Linux 2.4 versions (usually -ac, currently 2.4.10ac3).
I'm using NVidia Xserver module, but it doesn't seem related (the lookup
occured with no X while starting gpm once or twice).

If I kill Xserver (haven't tried with gpm), the keyboard (and mouse) start
working again (the next Xserver spawn works fine).

For me, it looks like some race condition between open_aux and mouse
(kbd?) interrupt, causing interrupts or kbd controller to stay disabled
after the mouse device is opened. The interrupt counters for both kbd
and psaux stay constant when I move the mouse and/or press buttons/keyboard
keys:

intrepid:~$ cat /proc/interrupts 
           CPU0       
  0:    1528212          XT-PIC  timer
  1:          6          XT-PIC  keyboard
  2:          0          XT-PIC  cascade
  3:     189554          XT-PIC  serial
  9:    1587447          XT-PIC  acpi, nvidia
 11:      15215          XT-PIC  usb-uhci, eth0, eth1
 12:          2          XT-PIC  PS/2 Mouse
 14:      49181          XT-PIC  ide0
 15:          1          XT-PIC  ide1
NMI:          0 
ERR:          3

I'm currently keeping this machine in locked state, so I can provide more
info.

What I also found is that open_aux routine isn't protected by lock_kernel(),
while release_aux is. Is that correct? Would a mouse interrupt received
before open_aux() is completed cause such a lookup?

-- 
Krzysztof Halasa
Network Administrator

^ permalink raw reply	[flat|nested] 5+ messages in thread
[parent not found: <200110112004.f9BK47b0070854@smtpzilla2.xs4all.nl>]
* Re: keyboard + PS/2 mouse locks after opening psaux
@ 2002-01-10 13:15 Donnie Roberts
  0 siblings, 0 replies; 5+ messages in thread
From: Donnie Roberts @ 2002-01-10 13:15 UTC (permalink / raw)
  To: linux-kernel

I just got a Tyan Tiger K7 and experienced a similar problem. The
keyboard locked up when gpm started, but it came back after I
stopped gpm (by logging in remotely). I discovered in my BIOS that
the mouse was configured to "Automatic". Changing it to "Enabled"
fixed my problem.

I suggest checking your BIOS for anything related to the mouse. It
could be occurring because the interrupt is not getting assigned
for the mouse by the BIOS, or something to that effect. That is
what my thoughts are on this problem. After seeing reports of the
interrupt counts in /proc/interrupts not being updated while the
mouse (/dev/psaux) is opened, it made me think that it could be an
IRQ problem.

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

end of thread, other threads:[~2002-01-10 13:15 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-10-09 10:21 keyboard + PS/2 mouse locks after opening psaux Krzysztof Halasa
2001-10-11 15:24 ` Marius Gedminas
2001-12-16  1:36 ` Krzysztof Halasa
     [not found] <200110112004.f9BK47b0070854@smtpzilla2.xs4all.nl>
2001-10-12 13:33 ` Marius Gedminas
2002-01-10 13:15 Donnie Roberts

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).