Discussions
Categories
- 385.5K All Categories
- 5.1K Data
- 2.5K Big Data Appliance
- 2.5K Data Science
- 453.4K Databases
- 223.2K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 47 Multilingual Engine
- 606 MySQL Community Space
- 486 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.2K ORDS, SODA & JSON in the Database
- 585 SQLcl
- 4K SQL Developer Data Modeler
- 188K SQL & PL/SQL
- 21.5K SQL Developer
- 46 Data Integration
- 46 GoldenGate
- 298.4K Development
- 4 Application Development
- 20 Developer Projects
- 166 Programming Languages
- 295K Development Tools
- 150 DevOps
- 3.1K QA/Testing
- 646.7K Java
- 37 Java Learning Subscription
- 37.1K Database Connectivity
- 201 Java Community Process
- 108 Java 25
- 22.2K Java APIs
- 138.3K Java Development Tools
- 165.4K Java EE (Java Enterprise Edition)
- 22 Java Essentials
- 176 Java 8 Questions
- 86K Java Programming
- 82 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 208 Java User Groups
- 25 JavaScript - Nashorn
- Programs
- 667 LiveLabs
- 41 Workshops
- 10.3K Software
- 6.7K Berkeley DB Family
- 3.6K JHeadstart
- 6K Other Languages
- 2.3K Chinese
- 207 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 474 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: 128 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.