summary refs log tree commit diff stats
path: root/results/classifier/gemma3:12b/peripherals/2860
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-07-03 07:27:52 +0000
committerChristian Krinitsin <mail@krinitsin.com>2025-07-03 07:27:52 +0000
commitd0c85e36e4de67af628d54e9ab577cc3fad7796a (patch)
treef8f784b0f04343b90516a338d6df81df3a85dfa2 /results/classifier/gemma3:12b/peripherals/2860
parent7f4364274750eb8cb39a3e7493132fca1c01232e (diff)
downloadqemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.tar.gz
qemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.zip
add deepseek and gemma results
Diffstat (limited to 'results/classifier/gemma3:12b/peripherals/2860')
-rw-r--r--results/classifier/gemma3:12b/peripherals/286034
1 files changed, 34 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/peripherals/2860 b/results/classifier/gemma3:12b/peripherals/2860
new file mode 100644
index 000000000..3509bf8e7
--- /dev/null
+++ b/results/classifier/gemma3:12b/peripherals/2860
@@ -0,0 +1,34 @@
+
+ps2 keyboard not work after boot and use libspice to connect it
+Description of problem:
+When I start almost 10 qemu virtual machines, there will always be one or two that have the ps2 keyboard not work well after booted.But I use mstsc to connect to the desktop, the keyboard works fine. But when reboot or migrate it well recovery.
+Steps to reproduce:
+1.Asynchronously start 40 qemu virtual machines, each with 4 cores and 4 threads
+
+2.there will always be one or two that have the ps2 keyboard not work well.
+
+4.And when i gdb debug it, i found i hang at the func "prepare_mmio_access"
+
+5.reboot or migrate it well recovery
+Additional information:
+the gdb debug as fllow:
+
+gdb attach $pid 
+
+gdb>b kbd_push_key      //spice input
+
+gdb>b kbd_read_data
+
+gdb>b ps2_keyboard_event
+
+gdb>c
+
+After continue, the code run on ps2_keyboard_event,but no work to "kbd_read_data".This Proves that the keyboard input has been added to the queue, but has not been read from the queue.
+
+gdb> thread 4   //switch to thread "CPU 0/KVM"
+
+gdb> bt
+
+![image](/uploads/82527d2b382cacd2d4e40793d78d3e59/image.png)
+
+I guess there is no event to notify the device to read after writing to the queue, or is it deadlocked? I'm not sure