Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OpenJDK BootstrapLogger/BootstrapLoggerTest crash vmState=0x00040000 #17349

Closed
pshipton opened this issue May 5, 2023 · 11 comments
Closed

OpenJDK BootstrapLogger/BootstrapLoggerTest crash vmState=0x00040000 #17349

pshipton opened this issue May 5, 2023 · 11 comments

Comments

@pshipton
Copy link
Member

pshipton commented May 5, 2023

https://openj9-jenkins.osuosl.org/job/Test_openjdk20_j9_sanity.openjdk_s390x_linux_Nightly/49
jdk_lang_j9_0
java/lang/System/LoggerFinder/internal/BootstrapLogger/BootstrapLoggerTest.java

https://openj9-artifactory.osuosl.org/artifactory/ci-openj9/Test/Test_openjdk20_j9_sanity.openjdk_s390x_linux_Nightly/49/openjdk_test_output.tar.gz

21:05:08  STDERR:
21:05:08  Testing: SECURE
21:05:08  Setting security manager
21:05:08  WARNING: A terminally deprecated method in java.lang.System has been called
21:05:08  WARNING: System::setSecurityManager has been called by BootstrapLoggerTest (file:/home/jenkins/workspace/Test_openjdk20_j9_sanity.openjdk_s390x_linux_Nightly/aqa-tests/TKG/output_16832443529850/jdk_lang_j9_0/work/classes/0/java/lang/System/LoggerFinder/internal/BootstrapLogger/BootstrapLoggerTest.d/)
21:05:08  WARNING: Please consider reporting this to the maintainers of BootstrapLoggerTest
21:05:08  WARNING: System::setSecurityManager will be removed in a future release
21:05:08  VM Booted: false
21:05:08  LogManager initialized: false
21:05:08  VM Booted: true
21:05:08  LogManager initialized: false
21:05:08  May 05, 2023 1:04:20 AM BootstrapLoggerTest main
21:05:08  INFO: LOG#4: VM now booted: true
21:05:08  May 05, 2023 1:04:20 AM jdk.internal.logger.BootstrapLogger$LogEvent log
21:05:08  INFO: Early message #1
21:05:08  May 05, 2023 1:04:20 AM jdk.internal.logger.BootstrapLogger$LogEvent log
21:05:08  WARNING: Early message #2
21:05:08  May 05, 2023 1:04:20 AM jdk.internal.logger.BootstrapLogger$LogEvent log
21:05:08  INFO: Early message #3
21:05:08  Unhandled exception
21:05:08  Type=Segmentation error vmState=0x00040000
21:05:08  J9Generic_Signal_Number=00000018 Signal_Number=0000000b Error_Value=00000000 Signal_Code=00000001
21:05:08  Handler1=000003FF8BAC96C8 Handler2=000003FF8B9B1998 InaccessibleAddress=0000000000000000
21:05:08  gpr0=0000000000000000 gpr1=0000000000000001 gpr2=0000000000000000 gpr3=0000000000000002
21:05:08  gpr4=000003FEF4008C10 gpr5=0000000000000000 gpr6=0000000000000002 gpr7=000000000000000A
21:05:08  gpr8=000003FEF4008C10 gpr9=000003FEF4008BE0 gpr10=000003FF8ADC2CD8 gpr11=000003FF8BD38C58
21:05:08  gpr12=0000000000000000 gpr13=00000000000000EB gpr14=000003FF8BAC29CE gpr15=000003FF8ADC29C8
21:05:08  psw=000003FF8BCA18DE mask=0705000180000000 fpc=00080000 bea=000003FF8BAC29C8
21:05:08  fpr0 000003fef00008f4 (f: 4026534144.000000, d: 2.170669e-311)
21:05:08  fpr1 000003ff8adc19a0 (f: 2329680384.000000, d: 2.171953e-311)
21:05:08  fpr2 0000000000000000 (f: 0.000000, d: 0.000000e+00)
21:05:08  fpr3 408a755555555555 (f: 1431655808.000000, d: 8.466667e+02)
21:05:08  fpr4 0000000000000007 (f: 7.000000, d: 3.458460e-323)
21:05:08  fpr5 3f7d8f891d50d1a2 (f: 491835808.000000, d: 7.216964e-03)
21:05:08  fpr6 000003fef0000960 (f: 4026534144.000000, d: 2.170669e-311)
21:05:08  fpr7 0000000000000000 (f: 0.000000, d: 0.000000e+00)
21:05:08  fpr8 0000000000000000 (f: 0.000000, d: 0.000000e+00)
21:05:08  fpr9 0000000000000000 (f: 0.000000, d: 0.000000e+00)
21:05:08  fpr10 000003ff8ad84000 (f: 2329427968.000000, d: 2.171953e-311)
21:05:08  fpr11 0000000000000000 (f: 0.000000, d: 0.000000e+00)
21:05:08  fpr12 0005fae7de6fa519 (f: 3731858688.000000, d: 8.316353e-309)
21:05:08  fpr13 000003feec01be68 (f: 3959537152.000000, d: 2.170636e-311)
21:05:08  fpr14 000003ff817465e0 (f: 2171889152.000000, d: 2.171875e-311)
21:05:08  fpr15 000003feec0b9dd8 (f: 3960184320.000000, d: 2.170636e-311)
21:05:08  Module=/home/jenkins/workspace/Test_openjdk20_j9_sanity.openjdk_s390x_linux_Nightly/openjdkbinary/j2sdk-image/lib/default/libj9vm29.so
21:05:08  Module_base_address=000003FF8BA80000
21:05:08  Target=2_90_20230504_52 (Linux 5.4.0-137-generic)
21:05:08  CPU=s390x (4 logical CPUs) (0x1f58f7000 RAM)
21:05:08  ----------- Stack Backtrace -----------
21:05:08  getSendSlotsFromSignature+0x1e (0x000003FF8BCA18DE [libj9vm29.so+0x2218de])
21:05:08  getNPEMessage+0x1786 (0x000003FF8BAC29CE [libj9vm29.so+0x429ce])
21:05:08  JVM_GetExtendedNPEMessage+0x164 (0x000003FF902A21D4 [libjvm.so+0x221d4])
21:05:08  ffi_call_SYSV+0x98 (0x000003FF8BD15498 [libj9vm29.so+0x295498])
21:05:08  ffi_call+0xa2 (0x000003FF8BD14EAA [libj9vm29.so+0x294eaa])
21:05:08  _ZN26VM_BytecodeInterpreterFull3runEP10J9VMThread+0x13a94 (0x000003FF8BB781E4 [libj9vm29.so+0xf81e4])
21:05:08  bytecodeLoopFull+0xee (0x000003FF8BB6473E [libj9vm29.so+0xe473e])
21:05:08  c_cInterpreter+0x64 (0x000003FF8BC8EFA4 [libj9vm29.so+0x20efa4])
21:05:08  ---------------------------------------
@pshipton
Copy link
Member Author

pshipton commented May 5, 2023

@tajila @ChengJin01 fyi

@tajila
Copy link
Contributor

tajila commented May 5, 2023

@JasonFengJ9 Can you please take a look at this

@JasonFengJ9 JasonFengJ9 self-assigned this May 5, 2023
@JasonFengJ9
Copy link
Member

JasonFengJ9 commented May 5, 2023

#12 <signal handler called>
#13 getSendSlotsFromSignature (signature=0x2 <error: Cannot access memory at address 0x2>) at /home/jenkins/workspace/Build_JDK20_s390x_linux_Nightly/openj9/runtime/util/sendslot.c:34
#14 0x000003ff8bac29ce in simulateStack (npeMsgData=0x3ff8adc2cd8) at /home/jenkins/workspace/Build_JDK20_s390x_linux_Nightly/openj9/runtime/vm/extendedMessageNPE.cpp:1625
#15 getNPEMessage (npeMsgData=<optimized out>) at /home/jenkins/workspace/Build_JDK20_s390x_linux_Nightly/openj9/runtime/vm/extendedMessageNPE.cpp:1349
#16 0x000003ff902a21d4 in JVM_GetExtendedNPEMessage (env=0x3ff8c58d400, throwableObj=0x3fef00088b0) at /home/jenkins/workspace/Build_JDK20_s390x_linux_Nightly/openj9/runtime/j9vm/javanextvmi.cpp:163
#17 0x000003ff8bd15498 in ffi_call_SYSV () from /home/jenkins/workspace/Test_openjdk20_j9_sanity.openjdk_s390x_linux_Nightly/openjdkbinary/j2sdk-image/lib/default/libj9vm29.so
#18 0x000003ff8bd14eaa in ffi_call (cif=<optimized out>, fn=<optimized out>, rvalue=<optimized out>, avalue=<optimized out>) at /home/jenkins/workspace/Build_JDK20_s390x_linux_Nightly/openj9/runtime/libffi/s390/ffi.c:532
#19 0x000003ff8bb781e4 in VM_BytecodeInterpreterFull::cJNICallout (isStatic=<optimized out>, function=<optimized out>, returnStorage=<optimized out>, returnType=<optimized out>, javaArgs=0x3ff00000000, receiverAddress=0x3fef00088b0, 
    _pc=<optimized out>, _sp=<optimized out>, this=<optimized out>) at /home/jenkins/workspace/Build_JDK20_s390x_linux_Nightly/openj9/runtime/vm/BytecodeInterpreter.hpp:2523
#20 VM_BytecodeInterpreterFull::callCFunction (returnType=<optimized out>, isStatic=<optimized out>, bp=<optimized out>, javaArgs=<optimized out>, receiverAddress=<optimized out>, jniMethodStartAddress=<optimized out>, _pc=<optimized out>, 
    _sp=<optimized out>, this=<optimized out>) at /home/jenkins/workspace/Build_JDK20_s390x_linux_Nightly/openj9/runtime/vm/BytecodeInterpreter.hpp:2341
#21 VM_BytecodeInterpreterFull::runJNINative (_pc=<optimized out>, _sp=<optimized out>, this=<optimized out>) at /home/jenkins/workspace/Build_JDK20_s390x_linux_Nightly/openj9/runtime/vm/BytecodeInterpreter.hpp:2231
#22 VM_BytecodeInterpreterFull::run (this=0x3ff8adc33e0, vmThread=<optimized out>) at /home/jenkins/workspace/Build_JDK20_s390x_linux_Nightly/openj9/runtime/vm/BytecodeInterpreter.hpp:10814

Apparently the signature=0x2 was bad and caused the segmentation error.

switch (signature[i]) {

Running a 50x grinder - https://openj9-jenkins.osuosl.org/job/Grinder/2314/ - this failure wasn't reproduced

@pshipton pshipton removed this from the Java 20.0.1 0.39 milestone May 9, 2023
@ThanHenderson
Copy link
Contributor

ThanHenderson commented Feb 16, 2024

I am experiencing this pretty consistently locally when trying to run DayTrader benchmarks on OJDK MH builds for JDK11.

Edit for context:
OpenJ9 SHA
5a29d29

ECLIPSE OMR SHA
0966eb360f6e0537e165426416051ac30c9afc65

JDK11
556d2a9dc7955cfa1e4bdd56b759224ca6c8cba6

@ChengJin01
Copy link

FYI: @fengxue-IS

@JasonFengJ9
Copy link
Member

I am experiencing this pretty consistently locally when trying to run DayTrader benchmarks on OJDK MH builds for JDK11.

@ThanHenderson is there a way to reproduce the failure?

@ThanHenderson
Copy link
Contributor

I am experiencing this pretty consistently locally when trying to run DayTrader benchmarks on OJDK MH builds for JDK11.

@ThanHenderson is there a way to reproduce the failure?

I was seeing it quite frequently, then it stopped occurring... I can try to reproduce.

@ThanHenderson
Copy link
Contributor

@JasonFengJ9 Oh, I see. The problem arises when a shared class cache is misused. In my case I have a script that specifies the shared class cache name, and I was running the the same cache for different builds. I don't think there is an underlying problem with the VM.

@pshipton
Copy link
Member Author

Except on Windows, if you attempt to use a shared cache that doesn't match the VM SHA, it should delete and recreate the cache.

@JasonFengJ9
Copy link
Member

Expect this issue to be fixed by

Closing

Copy link

Issue Number: 17349
Status: Closed
Actual Components: comp:vm, test failure
Actual Assignees: No one :(
PR Assignees: JasonFengJ9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants