Bug 4564

Summary: Mouse hang after switching to other host using a kvm
Product: Drivers Reporter: Ga (gael.roualland)
Component: Input DevicesAssignee: Dmitry Torokhov (dmitry.torokhov)
Status: REJECTED UNREPRODUCIBLE    
Severity: normal CC: bunk, protasnb, vojtech
Priority: P2    
Hardware: i386   
OS: Linux   
Kernel Version: 2.6.11.7 Subsystem:
Regression: Yes Bisected commit-id:

Description Ga 2005-04-30 06:37:44 UTC
Distribution: Debian Sarge
Hardware Environment: x86 SMP + KVM
Software Environment: Linux 2.6.11.x, XFree86 4.3, GPM
Problem Description:
Since 2.6.11 at least (I think 2.6.10 was OK, but I'm not sure as I'm not using
the kvm very often), when switching to another host with the kvm then switching
back to the linux host, the mouse doesn't move anymore under X or console (gpm).
No kernel messages about lost of sync or anything. Unloading/reloading the
psmouse module makes things work again.
The other host (running FreeBSD) is not affected so the mouse is probably doing OK.
From what psmouse says "input: PS/2 Logitech Mouse on isa0060/serio1", I assume
the protocol to be bare PS2.

Steps to reproduce:
Switch to other host, then switch back to linux host.
Comment 1 Ga 2005-04-30 08:39:12 UTC
Sorry, did not see bug 2082...

*** This bug has been marked as a duplicate of 2082 ***
Comment 2 Dmitry Torokhov 2005-05-06 18:37:44 UTC
Ugh, can't reopen it, you'll have to do it. 
 
Anyway, this bug is different from 2082 as you don't seem to get any data from 
the mouse once you switched as opposed to getting wrong data. I wonder if 
logitech probe confuses your KVM. 
 
Does it help if you add "options psmouse proto=exps" to 
your /etc/modprobe.conf ? 
 
Comment 3 Ga 2005-05-07 04:02:41 UTC
Hello,
The mouse works with proto=exps, but the switching from the kvm still locks it...
On the other host, the mouse is doing fine...

I'm starting to wonder if there is not something wrong with the kvm, so I'll try
with some older kernels to see if I can refind a version where that was OK.

Ga
Comment 4 Ga 2005-05-07 06:30:33 UTC
I downgraded to 2.6.10, and everything is OK, which confirms the problem
appeared with 2.6.11. Hope that helps...
Comment 6 Ga 2005-05-10 16:21:50 UTC
Hello,
I tried both patches but unfortunately no, it doesn't help...
Comment 7 Natalie Protasevich 2007-11-05 21:36:04 UTC
Gael,
Have you tested with recent kernels since, is the problem still there?
Thanks.