JDK-8209415 : Fix JVMTI test failure HS202
  • Type: Bug
  • Component: hotspot
  • Sub-Component: jvmti
  • Affected Version: 11,12
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: linux
  • CPU: aarch64
  • Submitted: 2018-08-13
  • Updated: 2021-02-01
  • Resolved: 2018-11-13
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 11 JDK 12 Other
11.0.11-oracleFixed 12 b20Fixed openjdk8u292Fixed
Related Reports
Duplicate :  
JDK-8256448 - hotswap/HS202/hs202t002/hs202t002.java failed with exit code 97 in aarch64
Relates :  
JDK-8257192 - Integrate AArch64 JIT port into 8u
Description
vmTestbase/nsk/jvmti/scenarios/hotswap/HS202/hs202t002/hs202t002.java

This JVMTI test failed because of a SIGBUS. It requires some background knowledge of JVMTI before investigating this failure.
Comments
Fix Request Request to backport this fix to jdk11u. The patch fixes JVMTI test failure HS202 in AArch64. It can be applied cleanly on jdk11u and has been verified with JTreg tests.
14-03-2019
Hi Serguei Please check the attachment. We didn't have mach5 test result link. We used the jtreg to run the test locally. Test command: jtreg -v:error,fail \ -jdk:/real-path/build/linux-aarch64-normal-server-slowdebug/images/jdk \ -nativepath:/real-path/build/linux-aarch64-normal-server-slowdebug/images/test/hotspot/jtreg/native \ jdk_src/test/hotspot/jtreg/vmTestbase/nsk/jvmti/scenarios/hotswap/HS202/hs202t002/hs202t002.java This issue is on aarch64 Linux.
10-09-2018
Hi Yang Zhang, Could you, please, attach the hs_err_pid7872.log? Do you have any mach5 test result link? How do you run the test, do you use the jtreg to run the test locally? What are the steps to reproduce this issue? Is it reproducible on Linux-x64?
06-09-2018
Hi Serguei More logs are listed as follows. 2 kinds of failures occur randomly First is exit code 97 (same as linaro test result http://openjdk.linaro.org/) --------------------------------------------- java.lang.AssertionError: [/home/penli01/jdk_src/build/linux-aarch64-normal-server-fastdebug/images/jdk/bin/java, -cp, /home/penli01/JTwork/classes/vmTestbase/nsk/jvmti/scenarios/hotswap/HS202/hs202t002/hs202t002.d:/home/penli01/JTwork/classes/vmTestbase:/home/penli01/JTwork/classes/test/lib, -Djava.library.path=/home/penli01/jdk_src/build/linux-aarch64-normal-server-fastdebug/images/test/hotspot/jtreg/native, -agentlib:hs202t002=pathToNewByteCode=./bin -waittime=5 package=nsk samples=100 mode=compiled, nsk.jvmti.scenarios.hotswap.HS202.hs202t002.hs202t002] exit code is 97 --------------------------------------------- Second is SIGBUS with exit code 134 --------------------------------------------- # A fatal error has been detected by the Java Runtime Environment: # SIGBUS (0x7) at pc=0x0000007200750002, pid=7872, tid=7894 # JRE version: OpenJDK Runtime Environment (12.0) (fastdebug build 12-internal+0-adhoc.penli01.jdksrc) Java VM: OpenJDK 64-Bit Server VM (fastdebug 12-internal+0-adhoc.penli01.jdksrc, mixed mode, tiered, compressed oops, g1 gc, linux-aarch64) Problematic frame: C 0x0000007200750002 # Core dump will be written. Default location: Core dumps may be processed with "/usr/share/apport/apport %p %s %c %d %P" (or dumping to /home/penli01/JTwork/scratch/core.7872) # An error report file with more information is saved as: /home/penli01/JTwork/scratch/hs_err_pid7872.log # If you would like to submit a bug report, please visit: http://bugreport.java.com/bugreport/crash.jsp # Current thread is 7894 Dumping core ... STDERR: java.lang.AssertionError: [/home/penli01/jdk_src/build/linux-aarch64-normal-server-fastdebug/images/jdk/bin/java, -cp, /home/penli01/JTwork/classes/vmTestbase/nsk/jvmti/scenarios/hotswap/HS202/hs202t002/hs202t002.d:/home/penli01/JTwork/classes/vmTestbase:/home/penli01/JTwork/classes/test/lib, -Djava.library.path=/home/penli01/jdk_src/build/linux-aarch64-normal-server-fastdebug/images/test/hotspot/jtreg/native, -agentlib:hs202t002=pathToNewByteCode=./bin -waittime=5 package=nsk samples=100 mode=compiled, nsk.jvmti.scenarios.hotswap.HS202.hs202t002.hs202t002] exit code is 134 ---------------------------------------------
06-09-2018
Hi Yang Zhang, Could you, please, add a link to this failure? Does it fail in a mach5 test run? Closing it as incomplete for now until you add the failure details with logs.
20-08-2018