JDK-6317822 : VolanoMark failed on Mustang b49 Sparc Solaris
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 6
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • OS: solaris_8
  • CPU: sparc
  • Submitted: 2005-08-30
  • Updated: 2010-08-19
  • Resolved: 2005-09-27
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.
JDK 6
6Resolved
Related Reports
Duplicate :  
Relates :  
Description
VolanoMark failed on Mustang b49 sparc Solaris after running for 4 days and 8 hours.
In b38, there was a similar problem reported in CR 6257178 that was closed.

hostname: ultraowl.sfbay
# uname -a         
SunOS ultraowl 5.8 Generic_108528-29 sun4u sparc SUNW,Ultra-4

# /usr/j2se/bin/java -d64 -version
java version "1.6.0-ea"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.6.0-ea-b49)
Java HotSpot(TM) 64-Bit Server VM (build 1.6.0-ea-b49, mixed mode)

flag used:
/usr/j2se/bin/java  -d64 -XX:CompileThreshold=100 -XX:+UseSerialGC

log file location:
/bt/VolanoMarkrun.17357.-d64
# tail vmarkserver.out
Unexpected Error
------------------------------------------------------------------------------
SIGSEGV (0xb) at pc=0xffffffff7d15cc00, pid=17533, tid=3468881

Do you want to debug the problem?

To debug, run 'dbx - 17533'; then switch to thread 3468881
Enter 'yes' to launch dbx automatically (PATH must include dbx)
Otherwise, press RETURN to abort...

Stack Trace:
(dbx) where t@3468881
current thread: t@3468881
  [1] _libc_nanosleep(0xffffffff587001b8, 0xffffffff587001a8, 0x0, 0x0, 0x0, 0x0), at 0xffffffff7efa4b68
  [2] _ti__nanosleep(0x64, 0x0, 0x10, 0x1b1, 0x4f, 0xffffffff7f320000), at 0xffffffff7f21dcd0
  [3] os::message_box(0x4e, 0xffffffff7d8f7020, 0x4e, 0x4e, 0xffffffff587002b0, 0x64), at 0xffffffff7d5d98b4
  [4] VMError::show_message_box(0xffffffff58700580, 0xffffffff7d8f7020, 0x7d0, 0x1f97d4, 0xffffffff7d769ae7, 0xffffffff7d882000), at 0xff
ffffff7d688898
  [5] VMError::report_and_die(0xffffffff58700580, 0xffffffff7d8e1958, 0xb400, 0xffffffff7d8f7800, 0xb800, 0x1), at 0xffffffff7d68763c
  [6] JVM_handle_solaris_signal(0x100890900, 0x8c00, 0xffffffff587008c0, 0x1, 0xffffffff7d15cc00, 0x10c00), at 0xffffffff7d1fff8c
  [7] __sighndlr(0xb, 0xffffffff58700ba0, 0xffffffff587008c0, 0xffffffff7d1ff600, 0x8000, 0x0), at 0xffffffff7f21edd8
  [8] sigacthandler(0xffffffff58701c50, 0x0, 0x0, 0x0, 0xffffffff587008c0, 0xb), at 0xffffffff7f21b668
  ---- called from signal handler with signal 11 (SIGSEGV) ------
  [9] ObjectMonitor::exit(0x100206568, 0xffffffff4c300ea0, 0x1002065a0, 0x1, 0x0, 0xffffffff7d908838), at 0xffffffff7d15cc00
  [10] SharedRuntime::complete_monitor_unlocking_C(0xffffffff6817c058, 0xffffffff58700f10, 0xffffffff6446f0c0, 0x26b784, 0x7fffffffac380e
, 0xffffffff587), at 0xffffffff7d6168d8
  [11] 0xffffffff781c573c(0x0, 0xffffffff6446f058, 0xffffffff6446f0c0, 0x4, 0xffffffff644710f8, 0xffffffff666d8bc8), at 0xffffffff781c573
b
  [12] 0xffffffff781e16f8(0xffffffff64471298, 0x100638b90, 0x100890900, 0x100890900, 0x0, 0xffffffff587007a1), at 0xffffffff781e16f7
  [13] 0xffffffff78000240(0xffffffff58701180, 0xffffffff58701630, 0xa, 0xffffffff72c42d40, 0xffffffff7806ed20, 0xffffffff58701428), at 0x
ffffffff7800023f
  [14] JavaCalls::call_helper(0xffffffff58701630, 0xa, 0xffffffff58701418, 0x100890900, 0x1, 0xffffffff72c42d40), at 0xffffffff7d189e38
  [15] JavaCalls::call_virtual(0xffffffff58701628, 0xffffffff72c45d60, 0xffffffff7d8f8fa0, 0xffffffff7d8f9150, 0xffffffff58701418, 0x1008
90900), at 0xffffffff7d418b50
  [16] JavaCalls::call_virtual(0xffffffff58701628, 0x1002d6520, 0x1002d6528, 0xffffffff7d8f8fa0, 0xffffffff7d8f9150, 0x100890900), at 0xf
fffffff7d23c204
  [17] thread_entry(0x100890900, 0x100890900, 0xc400, 0xffffffff72c45d60, 0xffffffff64471298, 0xffffffff7d8f84f8), at 0xffffffff7d24e1cc
  [18] JavaThread::run(0x100890900, 0xd288, 0x0, 0xe800, 0x0, 0xffffffff7d882000), at 0xffffffff7d2496d8
  [19] java_start(0x100890900, 0x8bf8, 0x2ac194, 0x1006efd50, 0xffffffff7d72baa0, 0xffffffff7d882000), at 0xffffffff7d5d5f8c

Comments
EVALUATION This has almost the exact same stack as 6307972 (which may also be a dup of 6257178).
27-09-2005

EVALUATION It is possible this is the same issue in 6317226 which was just fixed and should make it into b51.
31-08-2005

EVALUATION If you follow the chain of bugs it appears the culprit if in fact this is a duplicate is a compiler bug.. See 6257178 which was closed a duplicate of 6288902. Al little confused as to which build it got fixed in.. I know it was not b48, we missed the gate for this build.. I think the commit to fix in build is wrong. Appears its fixed in b43 according to bugster.. Not sure though.
31-08-2005