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

Load_Level_2.mauve crash vmState=0x00040000 #19795

Open
pshipton opened this issue Jul 3, 2024 · 2 comments
Open

Load_Level_2.mauve crash vmState=0x00040000 #19795

pshipton opened this issue Jul 3, 2024 · 2 comments
Labels
segfault Issues that describe segfaults / JVM crashes test failure

Comments

@pshipton
Copy link
Member

pshipton commented Jul 3, 2024

Internal build
[Linux S390 64bit Compressed Pointers] 80 Load_Level_2.mauve.5mins.Mode551
-XX:+UseCompressedOops -Xjit -Xgcpolicy:balanced
rtv-rhel8s390x-svl-test-71dt6-1

60x grinders passed

j> 07:25:32 Type=Segmentation error vmState=0x00040000
j> 07:25:32 J9Generic_Signal_Number=00000018 Signal_Number=0000000b Error_Value=00000000 Signal_Code=00000002
j> 07:25:32 Handler1=000003FFA2F60720 Handler2=000003FFA2CAC110 InaccessibleAddress=000003FF112C8000
j> 07:25:32 gpr0=0000000000000000 gpr1=0000000000004F50 gpr2=0000000000000000 gpr3=0000000000000014
j> 07:25:32 gpr4=0000000000000010 gpr5=0000000000000008 gpr6=0000000000000000 gpr7=000003FFFAEFD968
j> 07:25:32 gpr8=000000000000000A gpr9=000003FF112C8E98 gpr10=0000000000000000 gpr11=000003FF13D550E8
j> 07:25:32 gpr12=000003FF13CA1BA0 gpr13=000003FF13B4C522 gpr14=000003FF112C8BF8 gpr15=000003FF112C8C00
j> 07:25:32 psw=000003FF112C8BF8 mask=0705000180000000 fpc=00080000 bea=000003FFA3B49268
j> 07:25:32 fpr0=000000000000000d (f: 13.000000, d: 6.422853e-323)
j> 07:25:32 fpr1=000003ffa3c9f968 (f: 2747922688.000000, d: 2.172159e-311)
j> 07:25:32 fpr2=000003ffa3f77000 (f: 2750902272.000000, d: 2.172161e-311)
j> 07:25:32 fpr3=0000000000000007 (f: 7.000000, d: 3.458460e-323)
j> 07:25:32 fpr4=000003ff7c12824c (f: 2081587840.000000, d: 2.171830e-311)
j> 07:25:32 fpr5=000003ff7c1282a0 (f: 2081587840.000000, d: 2.171830e-311)
j> 07:25:32 fpr6=0000000000000000 (f: 0.000000, d: 0.000000e+00)
j> 07:25:32 fpr7=fa17371aaba46d6c (f: 2879679744.000000, d: -1.316890e+280)
j> 07:25:32 fpr8=0000000000000000 (f: 0.000000, d: 0.000000e+00)
j> 07:25:32 fpr9=0000000000000000 (f: 0.000000, d: 0.000000e+00)
j> 07:25:32 fpr10=000003ff3c01fa70 (f: 1006762624.000000, d: 2.171299e-311)
j> 07:25:32 fpr11=000003fff817e568 (f: 4162315520.000000, d: 2.172858e-311)
j> 07:25:32 fpr12=000003ff112cc910 (f: 288147712.000000, d: 2.170944e-311)
j> 07:25:32 fpr13=000002aa6a8e4710 (f: 1787709184.000000, d: 1.448084e-311)
j> 07:25:32 fpr14=0000000000041000 (f: 266240.000000, d: 1.315400e-318)
j> 07:25:32 fpr15=000003fff817d4a0 (f: 4162311424.000000, d: 2.172858e-311)
j> 07:25:32 Target=2_90_20240703_73929 (Linux 4.18.0-553.5.1.el8_10.s390x)
j> 07:25:32 CPU=s390x (4 logical CPUs) (0x1f6613000 RAM)
j> 07:25:32 ----------- Stack Backtrace -----------
@pshipton pshipton added test failure segfault Issues that describe segfaults / JVM crashes labels Jul 3, 2024
@dmitripivkine
Copy link
Contributor

Looks like this is some kind of run-time virtual memory error, can be machine issue. InaccessibleAddress=000003FF112C8000 is aligned to 4K page border and requested address is inside this page. The page was not accessible at the time of crash. Any way, this page is included to the system core and has non-zero values in it.

@dmitripivkine
Copy link
Contributor

Also this virtual memory interval is not Read Only:

0x000003ff1128d000	0x000003ff112ccfff	0x0000000000040000	(262,144)                  	RW

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
segfault Issues that describe segfaults / JVM crashes test failure
Projects
None yet
Development

No branches or pull requests

2 participants