summary refs log tree commit diff stats
path: root/results/classifier/118/unknown/1862874
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/118/unknown/1862874')
-rw-r--r--results/classifier/118/unknown/1862874135
1 files changed, 135 insertions, 0 deletions
diff --git a/results/classifier/118/unknown/1862874 b/results/classifier/118/unknown/1862874
new file mode 100644
index 000000000..91b0f5609
--- /dev/null
+++ b/results/classifier/118/unknown/1862874
@@ -0,0 +1,135 @@
+KVM: 0.877
+virtual: 0.849
+register: 0.839
+performance: 0.836
+user-level: 0.812
+permissions: 0.804
+debug: 0.803
+mistranslation: 0.802
+graphic: 0.801
+risc-v: 0.800
+x86: 0.797
+TCG: 0.795
+device: 0.785
+VMM: 0.778
+architecture: 0.777
+vnc: 0.774
+ppc: 0.771
+boot: 0.763
+hypervisor: 0.763
+assembly: 0.751
+semantic: 0.750
+peripherals: 0.747
+network: 0.744
+arm: 0.741
+socket: 0.730
+i386: 0.712
+kernel: 0.711
+files: 0.704
+PID: 0.680
+
+java may stuck for a long time in system mode with "-cpu max"
+
+Bug Description:
+Run "java -version" in guest VM, java may stuck for a long time (several hours) and then recover.
+
+Steps to reproduce:
+1. Launch VM by attached simple script: launch.sh
+2. Execute "java -version" and then print "date" in a loop
+    while :
+    do
+      /home/bot/jdk/bin/java -version
+      date
+    done
+3. A long time gap will be observed: may > 24 hours.
+
+Technical details:
+* host: x86_64 Linux 4.15.0-70-generic
+* qemu v4.2.0
+* java: tried two versions: openjdk-11-jre-headless or compiled java-13 
+* command-line: (See details in launch.sh)
+/home/bot/qemu/qemu-build/qemu-4.2.0/binaries/bin/qemu-system-x86_64 \
+  -drive "file=${img},format=qcow2" \
+  -drive "file=${user_data},format=raw" \
+  -cpu max \
+  -m 24G \
+  -serial mon:stdio \
+  -smp 8 \
+  -nographic \
+;
+
+* Observed by java core dump generated by "kill -SIGSEGV" when java stucked:
+Different pthreads are blocked on their own condition variables:
+
+  Id   Target Id         Frame
+  1    Thread 0x7f48a041a080 (LWP 22470) __GI_raise (sig=sig@entry=6)
+    at ../sysdeps/unix/sysv/linux/raise.c:51
+  2    Thread 0x7f487197d700 (LWP 22473) 0x00007f489f5c49f3 in futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x7f48980197c0)
+    at ../sysdeps/unix/sysv/linux/futex-internal.h:88
+  3    Thread 0x7f4861b89700 (LWP 22483) 0x00007f489f5c4ed9 in futex_reltimed_wait_cancelable (private=<optimized out>, reltime=0x7f4861b88960, expected=0,
+    futex_word=0x7f489801b084)
+    at ../sysdeps/unix/sysv/linux/futex-internal.h:142
+  4    Thread 0x7f4861e8c700 (LWP 22480) 0x00007f489f5c76d6 in futex_abstimed_wait_cancelable (private=0, abstime=0x0, expected=0, futex_word=0x7f48980107c0)
+    at ../sysdeps/unix/sysv/linux/futex-internal.h:205
+  5    Thread 0x7f4861c8a700 (LWP 22482) 0x00007f489f5c4ed9 in futex_reltimed_wait_cancelable (private=<optimized out>, reltime=0x7f4861c89800, expected=0,
+    futex_word=0x7f489801ed44)
+    at ../sysdeps/unix/sysv/linux/futex-internal.h:142
+  6    Thread 0x7f48a0418700 (LWP 22471) 0x00007f4880b13200 in ?? ()
+  7    Thread 0x7f48703ea700 (LWP 22478) 0x00007f489f5c49f3 in futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x7f489801dfc0)
+    at ../sysdeps/unix/sysv/linux/futex-internal.h:88
+  8    Thread 0x7f48702e9700 (LWP 22479) 0x00007f489f5c49f3 in futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x7f489838cd84)
+    at ../sysdeps/unix/sysv/linux/futex-internal.h:88
+  9    Thread 0x7f4870f71700 (LWP 22475) 0x00007f489f5c49f3 in futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x7f489801a300)
+    at ../sysdeps/unix/sysv/linux/futex-internal.h:88
+  10   Thread 0x7f487187b700 (LWP 22474) 0x00007f489f5c76d6 in futex_abstimed_wait_cancelable (private=0, abstime=0x0, expected=0, futex_word=0x7f48980cf770)
+    at ../sysdeps/unix/sysv/linux/futex-internal.h:205
+  11   Thread 0x7f4871a7f700 (LWP 22472) 0x00007f489f5c76d6 in futex_abstimed_wait_cancelable (private=0, abstime=0x0, expected=0, futex_word=0x7f489809ba30)
+    at ../sysdeps/unix/sysv/linux/futex-internal.h:205
+  12   Thread 0x7f4861d8b700 (LWP 22481) 0x00007f489f5c4ed9 in futex_reltimed_wait_cancelable (private=<optimized out>, reltime=0x7f4861d8a680, expected=0,
+    futex_word=0x7f489801ed44)
+    at ../sysdeps/unix/sysv/linux/futex-internal.h:142
+  13   Thread 0x7f48704ec700 (LWP 22477) 0x00007f489f5c4ed9 in futex_reltimed_wait_cancelable (private=<optimized out>, reltime=0x7f48704eb910, expected=0,
+    futex_word=0x7f489801d120)
+    at ../sysdeps/unix/sysv/linux/futex-internal.h:142
+  14   Thread 0x7f4870e6f700 (LWP 22476) 0x00007f489f5c4ed9 in futex_reltimed_wait_cancelable (private=<optimized out>, reltime=0x7f4870e6eb20, expected=0,
+    futex_word=0x7f489828abd0)
+    at ../sysdeps/unix/sysv/linux/futex-internal.h:142
+
+
+
+Have you tried with KVM ("-M accel=kvm")?
+
+Please try "strace -o /var/tmp/java.log -f java -version" and upload the strace.  If the strace is very large, it's probably safe to remove everything after around 10 seconds.
+
+The QEMU project is currently moving its bug tracking to another system.
+For this we need to know which bugs are still valid and which could be
+closed already. Thus we are setting the bug state to "Incomplete" now.
+
+If the bug has already been fixed in the latest upstream version of QEMU,
+then please close this ticket as "Fix released".
+
+If it is not fixed yet and you think that this bug report here is still
+valid, then you have two options:
+
+1) If you already have an account on gitlab.com, please open a new ticket
+for this problem in our new tracker here:
+
+    https://gitlab.com/qemu-project/qemu/-/issues
+
+and then close this ticket here on Launchpad (or let it expire auto-
+matically after 60 days). Please mention the URL of this bug ticket on
+Launchpad in the new ticket on GitLab.
+
+2) If you don't have an account on gitlab.com and don't intend to get
+one, but still would like to keep this ticket opened, then please switch
+the state back to "New" or "Confirmed" within the next 60 days (other-
+wise it will get closed as "Expired"). We will then eventually migrate
+the ticket automatically to the new system (but you won't be the reporter
+of the bug in the new system and thus you won't get notified on changes
+anymore).
+
+Thank you and sorry for the inconvenience.
+
+
+[Expired for QEMU because there has been no activity for 60 days.]
+