Issues with JDK 9 crashing itself and the operating system

Tue Oct 10 12:59:36 UTC 2017

Hello Rohit
Do you have any update regarding the cause of this? Looks like it is
specific to Ryzen+Linux.

On 25 September 2017 at 20:33, Rohit Arul Raj <rohitarulraj at gmail.com>
wrote:

> Hello Jeronimo,
>
> Thanks for the detailed report. We were able to reproduce the issue on
> our machine.
> We will analyze this further and get back to you.
>
> Regards,
> Rohit
>
> On Sat, Sep 23, 2017 at 4:46 PM, Jeronimo Backes <jbax at univocity.com>
> wrote:
> > Hello, my name is Jeronimo and I'm the author of the univocity-parsers
> > library (https://github.com/uniVocity/univocity-parsers) and I'm
> writing to
> > you by recommendation of Erik Duveblad.
> >
> > Basically, I recently installed the JDK 9 distributed by Oracle on my
> > development computer and when I try to build my project (with a simple
> `mvn
> > clean install` command) the JVM crashes with:
> >
> >
> > # A fatal error has been detected by the Java Runtime Environment:
> > #
> > #  SIGSEGV (0xb) at pc=0x00007f18b96c52f0, pid=3865, tid=3904
> > #
> > # JRE version: Java(TM) SE Runtime Environment (9.0+181) (build 9+181)
> > # Java VM: Java HotSpot(TM) 64-Bit Server VM (9+181, mixed mode, tiered,
> > compressed oops, g1 gc, linux-amd64)
> > # Problematic frame:
> > # V  [libjvm.so+0x9292f0]
> > JVMCIGlobals::check_jvmci_flags_are_consistent()+0x120
> > #
> > # Core dump will be written. Default location: Core dumps may be
> processed
> > with "/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %e" (or
> dumping to
> > /home/jbax/dev/repository/univocity-parsers/core.3865)
> > #
> > # An error report file with more information is saved as:
> > # /home/jbax/dev/repository/univocity-parsers/hs_err_pid3865.log
> > #
> > # Compiler replay data is saved as:
> > # /home/jbax/dev/repository/univocity-parsers/replay_pid3865.log
> > #
> > # If you would like to submit a bug report, please visit:
> > #   http://bugreport.java.com/bugreport/crash.jsp
> > #
> >
> >
> > The hs_err files generated are available here
> > https://github.com/uniVocity/univocity-parsers/files/
> 1326484/jdk_9_crash2.zip.
> > This zip also contains the pom.xml file I used. The build succeeded 4
> times
> > before the JVM crashed.
> >
> > Yesterday I had the crash happen 100% of the time, but the CPU was
> > overclocked to 3.6Ghz (never had any issue with it though) and saved the
> > error file here:
> > https://github.com/uniVocity/univocity-parsers/files/
> 1324326/jdk_9_crash.zip.
> > I created an issue on github to investigate this:
> > https://github.com/uniVocity/univocity-parsers/issues/189. There Erik
> > mentioned that:
> >
> > "Looking at the hs_err file, the stack trace is "wrong", a C2 Compiler
> > Thread can't call JVMCIGlobals::check_jvmci_flags_are_consistent (and
> the
> > value of the register RIP does not correspond to any instruction in the
> > compiled version of that function). This makes me suspect that something
> > could be wrong with your CPU, the CPU should not have jumped to this
> memory
> > location."
> >
> > Things still fail with stock hardware settings. More details about my
> > environment :
> >
> > OS, Maven and Java versions:
> >
> > [jbax at linux-pc ~]$ mvn -version
> > Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1;
> > 2014-12-15T03:59:23+10:30)
> > Maven home: /home/jbax/dev/apache-maven
> > Java version: 9, vendor: Oracle Corporation
> > Java home: /home/jbax/dev/jdk9
> > Default locale: en_AU, platform encoding: UTF-8
> > OS name: "linux", version: "4.12.13-1-manjaro", arch: "amd64", family:
> > "unix"
> > [jbax at linux-pc ~]$
> >
> > Hardware:
> > [jbax at linux-pc univocity-parsers]$ lscpu
> > Architecture:        x86_64
> > CPU op-mode(s):      32-bit, 64-bit
> > Byte Order:          Little Endian
> > CPU(s):              16
> > On-line CPU(s) list: 0-15
> > Thread(s) per core:  2
> > Core(s) per socket:  8
> > Socket(s):           1
> > NUMA node(s):        1
> > Vendor ID:           AuthenticAMD
> > CPU family:          23
> > Model:               1
> > Model name:          AMD Ryzen 7 1700 Eight-Core Processor
> > Stepping:            1
> > CPU MHz:             1550.000
> > CPU max MHz:         3000.0000
> > CPU min MHz:         1550.0000
> > BogoMIPS:            6001.43
> > Virtualization:      AMD-V
> > L1d cache:           32K
> > L1i cache:           64K
> > L2 cache:            512K
> > L3 cache:            8192K
> > NUMA node0 CPU(s):   0-15
> > Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> > mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext
> fxsr_opt
> > pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid
> extd_apicid
> > aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe
> popcnt
> > aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm
> > sse4a misalignsse 3dnowprefetch osvw skinit wdt tce topoext perfctr_core
> > perfctr_nb bpext perfctr_l2 mwaitx hw_pstate vmmcall fsgsbase bmi1 avx2
> smep
> > bmi2 rdseed adx smap clflushopt sha_ni xsaveopt xsavec xgetbv1 xsaves
> clzero
> > irperf arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid
> > decodeassists pausefilter pfthreshold avic overflow_recov succor smca
> >
> > On an unrelated note, I use an old java application that crashes the
> entire
> > OS for me when Java 9 is used: http://www.jinchess.com/download
> >
> > It's just a matter of downloading, unpacking and trying to start it with
> > jin-2.14.1/jin
> >
> > The OS crashes and I have to hard-reset the computer. It works just fine
> if
> > revert back to Java 6, 7 or 8.
> >
> > I thought you'd might want to investigate what is going on. Let me know
> if
> > you need more information.
> >
> > Best regards,
> >
> > Jeronimo.
> >
> >
> >
> >
> > --
> > the uniVocity team
> > www.univocity.com
>

-- 
the uniVocity team
www.univocity.com