Bug 5689 - java crashes with "JVMDG218: JVM is not fully initialized - will not do dump processing. Segmentation fault" on kernel 2.6.15-rc4
Summary: java crashes with "JVMDG218: JVM is not fully initialized - will not do dump ...
Status: REJECTED INVALID
Alias: None
Product: Platform Specific/Hardware
Classification: Unclassified
Component: PPC-64 (show other bugs)
Hardware: i386 Linux
: P2 normal
Assignee: Anton Blanchard
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-01 22:29 UTC by Fang Wenqi
Modified: 2006-11-13 05:13 UTC (History)
8 users (show)

See Also:
Kernel Version: 2.6.15-rc4
Subsystem:
Regression: ---
Bisected commit-id:


Attachments
kernel configuration file (33.50 KB, text/plain)
2005-12-01 23:32 UTC, Fang Wenqi
Details

Description Fang Wenqi 2005-12-01 22:29:56 UTC
Distribution:
  SLES9 SP4 plus kernel 2.6.15-rc4

Hardware Environment:
  IBM OpenPower 720

Software Environment:
  IBMJava2-1.4.2 is installed automatically by SLES9.	  
  
Problem Description:
  Issue java -version, then it reports:
  JVMDG218: JVM is not fully initialized - will not do dump processing.
  Segmentation fault

Steps to reproduce:
  ~#java -version
  JVMDG218: JVM is not fully initialized - will not do dump processing.
  Segmentation fault

Additional information:
  1. I cannot run any java problem at this time.
  ~#java hello         
  JVMDG218: JVM is not fully initialized - will not do dump processing.
  Segmentation fault

  2. Disable JIT is a work around for this problem.
  ~#export JAVA_COMPILER=none 
  ~#java -version
  Warning: JIT compiler "none" not found. Will use interpreter.
  java version "1.4.2"
  Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2)
  Classic VM (build 1.4.2, J2RE 1.4.2 IBM build cxp641420ifx-20040722    
  (142GA+75755) (JIT disabled))

  ~#java hello             
  Warning: JIT compiler "none" not found. Will use interpreter.
  Hello World
Comment 1 Olof Johansson 2005-12-01 22:43:08 UTC
Please attach the configuration file you used to build the kernel with.

When was the last time the test worked properly?
Comment 2 Fang Wenqi 2005-12-01 23:32:32 UTC
Created attachment 6746 [details]
kernel configuration file

I just testing kernel 2.6.15-rc2/rc3/rc4 on SLES9 SP4 this week, java failed on
all of them. I'm trying 2.6.14 now, will get the latest workable kernel and
post result here.
Comment 3 Fang Wenqi 2005-12-02 05:50:57 UTC
Correct myself, I'm testing on SLES9 SP3-rc, not SP4.
Comment 4 Fang Wenqi 2005-12-02 07:00:09 UTC
Tested linux-2.6.12, it met the same problem as 2.6.15. 
System encountered scsi error when booting with linux-2.6.9.

java works well with SLES default kernel 2.6.5-7.241-pseries64. I'll pick up
another machine to try linux-2.6.5 next Monday.

Comment 5 Ding Rui 2005-12-04 18:04:37 UTC
This problem reproduced on 2.6.15-rc4 (SLES9 SP4)
Comment 6 Ding Rui 2005-12-04 18:09:08 UTC
Oh,correct it.
This problem reproduced on 2.6.15-rc4 (SLES9 SP3)
not SLES9 SP4.
Comment 7 Fang Wenqi 2005-12-06 04:54:39 UTC
In reply to comment #1:
>When was the last time the test worked properly?

After testing, IBM java works on linux-2.6.11, however, fails on linux-2.6.12.
Hope this information is helpful for tracking the problem.

hv41-lp2:~ # java -version
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2)
Classic VM (build 1.4.2, J2RE 1.4.2 IBM build cxp641420ifx-20040722
(142GA+75755) (JIT enabled: jitc))
hv41-lp2:~ # uname -r
2.6.11
hv41-lp2:~ # cat /etc/SuSE-release 
SUSE LINUX Enterprise Server 9 (ppc)
VERSION = 9
PATCHLEVEL = 3



Comment 8 Anton Blanchard 2006-01-08 17:48:57 UTC
Can you test with after running:

ulimit -s unlimited

I think the address space changes went in around that time, and ulimit -s
unlimited will force the old layout.
Comment 9 James He 2006-01-10 22:52:58 UTC
Anton,

I tested it as you said on the stable kernel 2.6.15. The problem reproduced on 
this kernel. 
Comment 10 Mike Ranweiler 2006-05-10 17:35:22 UTC
This is a java problem, fixed in the next release (of java).  It evidently
started after the noexec feature was added.  Can probably be closed, now.

Note You need to log in before you can comment on or make changes to this bug.