openjdk crash on linux kernel 6.1.5

[yangfei at iscas.ac.cn]

Hi,

  The call trace looks the same as the one in your previous e-mail. 
  From the calltrace, I don't think this is an issue of the OpenJDK, but more likely an issue of the system. 
  Can you create some simple C/C++ program to exercise __vdso_clock_gettime() system call in your qemu system? 

Thanks,
Fei

-----Original Messages-----
From:"Ze Zhang" <zhangze.linux at gmail.com>
Sent Time:2023-01-31 15:14:13 (Tuesday)
To: riscv-port-dev at openjdk.org, sw-dev at groups.riscv.org
Cc: 
Subject: openjdk crash on linux kernel 6.1.5

hi,   on kernel 6.1.5,  java -version crashes:  
  
  Type "apropos word" to search for commands related to "word"...
Reading symbols from java...
Reading symbols from /usr/lib/jvm/java-20+gitAUTOINC+5dfc4ec7d9-openjdk-riscv64/bin/.debug/java...
(gdb) run -version
Starting program: /usr/bin/java -version
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".




[New Thread 0x7ffff6086180 (LWP 543)]
[New Thread 0x7ffff4c56180 (LWP 544)]
[New Thread 0x7ffff4a54180 (LWP 545)]
[New Thread 0x7ffff4852180 (LWP 546)]
[New Thread 0x7fffbdbfb180 (LWP 547)]
[New Thread 0x7fffbd9f9180 (LWP 548)]
[New Thread 0x7fffbd776180 (LWP 549)]

Thread 2 "java" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff6086180 (LWP 543)]
0x00007ffff7fdf916 in __vdso_clock_gettime ()
(gdb) 
(gdb) 
(gdb) 
(gdb) 
(gdb) bt
#0  0x00007ffff7fdf916 in __vdso_clock_gettime ()
#1  0x00007ffff7f1e712 in __GI___clock_gettime (clock_id=<optimized out="">, tp=<optimized out="">) at /usr/src/debug/glibc/2.36-r0/sysdeps/unix/sysv/linux/clock_gettime.c:42
#2  0xaa140004aa140003 in ?? ()
(gdb) 
Broadcast message from systemd-journald at qemuriscv64 (Tue 2022-12-20 18:46:12 UTC):

systemd[1]: Caught <segv> from PID 4.


Message from syslogd at qemuriscv64 at Tue Dec 20 18:46:12 2022 ...
systemd[1]: Caught <segv> from PID 4.

Broadcast message from systemd-journald at qemuriscv64 (Tue 2022-12-20 18:46:12 UTC):

systemd[1]: Caught <segv>, dumped core as pid 554.


Broadcast message from systemd-journald at qemuriscv64 (Tue 2022-12-20 18:46:12 UTC):

systemd[1]: Freezing execution.


Message from syslogd at qemuriscv64 at Tue Dec 20 18:46:12 2022 ...
systemd[1]: Caught <segv>, dumped core as pid 554.

Message from syslogd at qemuriscv64 at Tue Dec 20 18:46:12 2022 ...
systemd[1]: Freezing execution.

#0  0x00007ffff7fdf916 in __vdso_clock_gettime ()
#1  0x00007ffff7f1e712 in __GI___clock_gettime (clock_id=<optimized out="">, tp=<optimized out="">) at /usr/src/debug/glibc/2.36-r0/sysdeps/unix/sysv/linux/clock_gettime.c:42
#2  0xaa140004aa140003 in ?? ()
(gdb) 

#2  0xaa140004aa140003 in ?? ()
(gdb)


</optimized></optimized></segv></segv></segv></segv></optimized></optimized></zhangze.linux at gmail.com>