* [Bug 1862874] [NEW] java may stuck for a long time in system mode with "-cpu max"
@ 2020-02-12 3:54 JZ
2020-03-06 11:13 ` [Bug 1862874] " Stefan Hajnoczi
` (3 more replies)
0 siblings, 4 replies; 5+ messages in thread
From: JZ @ 2020-02-12 3:54 UTC (permalink / raw)
To: qemu-devel
Public bug reported:
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
** Affects: qemu
Importance: Undecided
Status: New
** Attachment added: "Launch guest VM"
https://bugs.launchpad.net/bugs/1862874/+attachment/5327528/+files/launch.sh
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1862874
Title:
java may stuck for a long time in system mode with "-cpu max"
Status in QEMU:
New
Bug description:
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1862874/+subscriptions
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug 1862874] Re: java may stuck for a long time in system mode with "-cpu max"
2020-02-12 3:54 [Bug 1862874] [NEW] java may stuck for a long time in system mode with "-cpu max" JZ
@ 2020-03-06 11:13 ` Stefan Hajnoczi
2021-03-30 8:37 ` David Hildenbrand
` (2 subsequent siblings)
3 siblings, 0 replies; 5+ messages in thread
From: Stefan Hajnoczi @ 2020-03-06 11:13 UTC (permalink / raw)
To: qemu-devel
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.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1862874
Title:
java may stuck for a long time in system mode with "-cpu max"
Status in QEMU:
New
Bug description:
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1862874/+subscriptions
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug 1862874] Re: java may stuck for a long time in system mode with "-cpu max"
2020-02-12 3:54 [Bug 1862874] [NEW] java may stuck for a long time in system mode with "-cpu max" JZ
2020-03-06 11:13 ` [Bug 1862874] " Stefan Hajnoczi
@ 2021-03-30 8:37 ` David Hildenbrand
2021-05-11 5:20 ` Thomas Huth
2021-07-11 4:17 ` Launchpad Bug Tracker
3 siblings, 0 replies; 5+ messages in thread
From: David Hildenbrand @ 2021-03-30 8:37 UTC (permalink / raw)
To: qemu-devel
** Changed in: qemu
Status: New => Confirmed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1862874
Title:
java may stuck for a long time in system mode with "-cpu max"
Status in QEMU:
Confirmed
Bug description:
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1862874/+subscriptions
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug 1862874] Re: java may stuck for a long time in system mode with "-cpu max"
2020-02-12 3:54 [Bug 1862874] [NEW] java may stuck for a long time in system mode with "-cpu max" JZ
2020-03-06 11:13 ` [Bug 1862874] " Stefan Hajnoczi
2021-03-30 8:37 ` David Hildenbrand
@ 2021-05-11 5:20 ` Thomas Huth
2021-07-11 4:17 ` Launchpad Bug Tracker
3 siblings, 0 replies; 5+ messages in thread
From: Thomas Huth @ 2021-05-11 5:20 UTC (permalink / raw)
To: qemu-devel
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.
** Changed in: qemu
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1862874
Title:
java may stuck for a long time in system mode with "-cpu max"
Status in QEMU:
Incomplete
Bug description:
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1862874/+subscriptions
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug 1862874] Re: java may stuck for a long time in system mode with "-cpu max"
2020-02-12 3:54 [Bug 1862874] [NEW] java may stuck for a long time in system mode with "-cpu max" JZ
` (2 preceding siblings ...)
2021-05-11 5:20 ` Thomas Huth
@ 2021-07-11 4:17 ` Launchpad Bug Tracker
3 siblings, 0 replies; 5+ messages in thread
From: Launchpad Bug Tracker @ 2021-07-11 4:17 UTC (permalink / raw)
To: qemu-devel
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1862874
Title:
java may stuck for a long time in system mode with "-cpu max"
Status in QEMU:
Expired
Bug description:
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1862874/+subscriptions
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2021-07-11 4:29 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-02-12 3:54 [Bug 1862874] [NEW] java may stuck for a long time in system mode with "-cpu max" JZ
2020-03-06 11:13 ` [Bug 1862874] " Stefan Hajnoczi
2021-03-30 8:37 ` David Hildenbrand
2021-05-11 5:20 ` Thomas Huth
2021-07-11 4:17 ` Launchpad Bug Tracker
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.