JDK-4937752 : vtest failed intermittenly when running with tiger b23 -server -Xcomp
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 5.0
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2003-10-15
  • Updated: 2009-11-16
  • Resolved: 2004-06-03
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
1.4.2_08Fixed
Related Reports
Duplicate :  
Relates :  
Description
vtest failed intermittenly (3/18000) when running with tiger b23 -server -Xcomp
The failure is reproducible. 
Test machine: j2se-app.west
# uname -a
SunOS j2se-app 5.9 Generic_114466-01 sun4u sparc SUNW,Sun-Fire

Java HotSpot(TM) Server VM (build 1.5.0-beta-b23, compiled mode)

The log files are under /bt/VolanoTestrun.22175.-server and will be moved
to /export/archive/tiger_b23/VolanoTestrun.22175.-server

#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
#  SIGBUS (0xa) at pc=0xf9015dcc, pid=16240, tid=180
#
# Java VM: Java HotSpot(TM) Server VM (1.5.0-beta-b23 compiled mode)
# Problematic frame:
# j  java.net.Socket.<init>(Ljava/net/SocketAddress;Ljava/net/SocketAddress;Z)V+
51
#

A bunch of threads have errors.
  [1] _libc_nanosleep(0x4, 0xec07ee30, 0x1, 0x0, 0x0, 0x4b4a2c), at 0xff31af64
  [2] _sleep(0x64, 0xfee4d6c6, 0x1, 0x0, 0x2cf, 0x2ce), at 0xff37e328
  [3] os::infinite_sleep(0xfeecef78, 0xfee4d6c6, 0x1, 0x1, 0x1, 0x64), at 0xfed5
6aa0
  [4] VMError::report_and_die(0xec07eff0, 0xfeecef78, 0xa, 0x0, 0x7400, 0x5000),
 at 0xfedd1c50
  [5] crash_handler(0xa, 0x0, 0xec07f1e8, 0x0, 0x0, 0x0), at 0xfedd2a28
  [6] __sighndlr(0xa, 0x0, 0xec07f1e8, 0xfedd29e4, 0x0, 0x0), at 0xff3861a0
  [7] call_user_handler(0xa, 0x0, 0xec07f1e8, 0x0, 0x0, 0x0), at 0xff37fed0
  [8] sigacthandler(0xa, 0x0, 0xec07f1e8, 0x8, 0xf68a98c0, 0x0), at 0xff380080
  ---- called from signal handler with signal 10 (SIGBUS) ------
  [9] 0xf9015dcc(0xf6e18a70, 0xb7, 0x0, 0xf9015ba0, 0xf68a98c0, 0xec07f528), at
0xf9015dcb
  [10] 0xf9005664(0xf6293a88, 0xb7, 0x0, 0xf9015e48, 0x80000000, 0xec07f5b0), at
 0xf9005663
  [11] 0xf9005664(0x0, 0x4729e0, 0x0, 0xf9015e48, 0xfee7c000, 0xec07f640), at 0x
f9005663
  [12] 0xf9063248(0xf6293960, 0xf0c06dd0, 0x2134, 0x1, 0x4729e0, 0xec07f710), at
 0xf9063247
  [13] 0xf90fb0cc(0xf6293960, 0xf0c06dd0, 0x2134, 0x471250, 0xfeece160, 0x0), at
 0xf90fb0cb
  [14] 0xf9071a44(0xf6293960, 0xb7, 0x8, 0x0, 0x80000000, 0xec07f710), at 0xf907
1a43
  [15] 0xf9005664(0xf0c216d0, 0xb7, 0x0, 0xf9015e48, 0x80000000, 0xec07f7a0), at
 0xf9005663
  [16] 0xf9005664(0xf6189ba8, 0xecc24570, 0x0, 0xf9015e00, 0x80000000, 0xec07f83
0), at 0xf9005663
  [17] 0xf9005b2c(0x0, 0xfeec7680, 0x0, 0xf90160a0, 0x709c, 0xec07f8a8), at 0xf9
005b2b
  [18] 0xf9000118(0xec07f990, 0xec07fb90, 0xa, 0xecc25318, 0xf900a6e0, 0xec07faa
8), at 0xf9000117
  [19] JavaCalls::call_helper(0x1, 0x4729e0, 0xec07faa0, 0xec07f9a0, 0x1, 0xf900
00c0), at 0xfe963f80
  [20] JavaCalls::call_virtual(0x6b70, 0x4729e0, 0x471258, 0x471264, 0x471260, 0
xf6189dd0), at 0xfea657fc
  [21] thread_entry(0xecc269e8, 0x4729e0, 0x471644, 0xfeee1da8, 0xfeee1e48, 0xfe
ee18c4), at 0xfea85754
  [22] JavaThread::run(0x4729e0, 0x1, 0x2, 0xfeebe1f8, 0xfeebe1f4, 0xec000000),
at 0xfea80780
  [23] _start(0x4729e0, 0x5800, 0x2709, 0x424c, 0xfee7c000, 0x4717c8), at 0xfea7
d6a8

###@###.### 2003-10-14

The problem is reproducible with b31. vtest failed intermittenly with b31 with
-server -Xcomp flags. Not sure if the failure in b31 is still the same as
bug 4937752.
core file is under /bt/VolanoTestrun.151.-server on machine bigapp-880-1.red.iplanet.com ( contact me for root passwd )

###@###.### 2003-12-16

It's easier to reproduce the bug using CMS GC.

###@###.### 2004-02-26


With b43, the failure happened in j2se-bigapps-b.west ( 12cpu* 1050MHZ, 96 GB memory )
1. ) In Tomcat run
flags used: -d64 -Xcomp
2> ) In Vtest run
flags used: -d64 -Xcomp -XX:+UseConcMarkSweepGC
3. ) In Vtest run
flags used: -server -Xcomp

###@###.### 2004-03-22
###@###.### 2004-11-16 20:42:36 GMT

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: tiger-beta2 tiger-rc FIXED IN: tiger-beta2 tiger-rc INTEGRATED IN: tiger-b54 tiger-beta2 tiger-rc
2004-06-14

SUGGESTED FIX http://analemma.sfbay.sun.com/net/prt-archiver.sfbay/export2/archived_workspaces/main/c2_baseline/2004/20040525153139.never.c1/workspace/webrevs/webrev-2004.05.26/src/share/vm/oops/cpCacheOop.hpp.diff.html
2004-06-11

EVALUATION Machine j2se-app.west can not be reached to evaluate bug. ###@###.### 2003-10-15 This was tracked down to cpCacheOopDesc::set_paramater_size overwriting the flags value with a TosState of 0. This caused the interpreter to select the wrong tos state, effectively pushing an extra value on the expression and eventually causing us to die. ###@###.### 2004-05-18
2004-05-18