Discussions
Categories
- 196.7K All Categories
- 2.2K Data
- 235 Big Data Appliance
- 1.9K Data Science
- 449.9K Databases
- 221.6K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 549 MySQL Community Space
- 478 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 532 SQLcl
- 4K SQL Developer Data Modeler
- 186.9K SQL & PL/SQL
- 21.3K SQL Developer
- 295.4K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.1K Development Tools
- 104 DevOps
- 3.1K QA/Testing
- 645.9K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 153 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 17 Java Essentials
- 158 Java 8 Questions
- 85.9K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.2K Java SE
- 13.8K Java Security
- 203 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 398 LiveLabs
- 37 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.6K Other Languages
- 2.3K Chinese
- 170 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 230 Portuguese
Oracle Java 1.8.0_172-b11 build 32-bit JVM on Oracle Linux 64-bit OS SIGSEGV (AMD-V only)
steven.saunders-Oracle
Member Posts: 119 Employee
May 5 06:00:24 obpcbpd2doc01 kernel: docfactory_supe[15268] bad frame in 32bit rt sig return frame:00000000f3405d70 ip:f716cc4d sp:d193c9c0 orax:ffffffffffffffff in libjvm.so[f6edf000+997000]
May 5 06:00:24 obpcbpd2doc01 abrt-hook-ccpp: Process 14839 (docfactory_supervisor) of user 5001 killed by SIGSEGV - dumping core
Might there be a bug fix for this in newer builds?
Update: This is further narrowed down to when AMD-V Virtualization is enabled, same does not Segmentation Fault on Intel or AMD (without AMD Virtualization enabled).
Answers
-
Customer has further tracked done that this SIGSEGV (Segmentation Fault) only happens with the AMD-V Virtualization is enabled on the image.