Here is a backtrace of the PS2 reset event:
#0 ps2_write_mouse (opaque=0x55804518ae30, val=255) at
/home/geoff/Projects/qemu/qemu/hw/input/ps2.c:1033
#1 0x00005580420e1dd9 in kbd_write_data (opaque=0x558045147aa0, addr=0,
val=255, size=1) at /home/geoff/Projects/qemu/qemu/hw/input/pckbd.c:357
#2 0x0000558041e7e64f in memory_region_write_accessor (mr=0x558045147ae0,
addr=0, value=0x7f9ec016f478, size=1, shift=0, mask=255, attrs=...)
at /home/geoff/Projects/qemu/qemu/memory.c:560
#3 0x0000558041e7e867 in access_with_adjusted_size (addr=0,
value=0x7f9ec016f478, size=1, access_size_min=1, access_size_max=1,
access_fn=0x558041e7e565 <memory_region_write_accessor>, mr=0x558045147ae0,
attrs=...) at /home/geoff/Projects/qemu/qemu/memory.c:627
#4 0x0000558041e814e9 in memory_region_dispatch_write (mr=0x558045147ae0,
addr=0, data=255, size=1, attrs=...)
at /home/geoff/Projects/qemu/qemu/memory.c:1503
#5 0x0000558041e31302 in flatview_write_continue (fv=0x7f9e90010c10, addr=96,
attrs=..., buf=0x7f9eee9de000 "\377\006", len=1, addr1=0, l=1,
mr=0x558045147ae0) at /home/geoff/Projects/qemu/qemu/exec.c:2900
#6 0x0000558041e31450 in flatview_write (fv=0x7f9e90010c10, addr=96,
attrs=..., buf=0x7f9eee9de000 "\377\006", len=1)
at /home/geoff/Projects/qemu/qemu/exec.c:2945
#7 0x0000558041e31827 in flatview_rw (fv=0x7f9e90010c10, addr=96, attrs=...,
buf=0x7f9eee9de000 "\377\006", len=1, is_write=true)
at /home/geoff/Projects/qemu/qemu/exec.c:3054
#8 0x0000558041e318df in address_space_rw (as=0x558042a4c940
<address_space_io>, addr=96, attrs=..., buf=0x7f9eee9de000 "\377\006", len=1,
is_write=true)
at /home/geoff/Projects/qemu/qemu/exec.c:3064
#9 0x0000558041e9617e in kvm_handle_io (port=96, attrs=...,
data=0x7f9eee9de000, direction=1, size=1, count=1)
at /home/geoff/Projects/qemu/qemu/accel/kvm/kvm-all.c:1698
#10 0x0000558041e968c2 in kvm_cpu_exec (cpu=0x5580444f4650) at
/home/geoff/Projects/qemu/qemu/accel/kvm/kvm-all.c:1938
#11 0x0000558041e670d9 in qemu_kvm_cpu_thread_fn (arg=0x5580444f4650) at
/home/geoff/Projects/qemu/qemu/cpus.c:1128
#12 0x00007f9ed49c5494 in start_thread (arg=0x7f9ec0172700) at
pthread_create.c:333
#13 0x00007f9ed4707aff in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1722884
Title:
keyboard input while mouse moving triggers mouse failure
Status in QEMU:
New
Bug description:
When QEMU is getting a ton of mouse input events if keys are pressed
on the keyboard the scan code will be corrupted causing erroneous
behavior. I have confirmed this problem in the latest version in git
(530049bc1dcc24c1178a29d99ca08b6dd08413e0).
After the erroneous behavior the operating system issues a keyboard
reset which prevents the mouse from functioning until the operating
system is restarted.
This seems to only occur if the PS2 mouse is being used as the input,
the tablet input device doesn't exhibit this behavior.
The same problem was reported here also:
https://openxt.atlassian.net/browse/OXT-562
Host : Debian 9
CPU : Ryzen 1700X
RAM : 16GB
Kernel: 4.12.0-0.bpo.2-amd64
Guest : Windows 10 (KVM)
RAM : 8GB (1GB Huge pages)
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1722884/+subscriptions
