hg: bsd-port/bsd-port/hotspot: 5 new changesets

[Greg Lewis]

On Mon, Nov 30, 2009 at 09:17:25AM -0500, Christos Zoulas wrote:
> On Nov 29,  8:31pm, glewis at eyesbeyond.com (Greg Lewis) wrote:
> -- Subject: Re: hg: bsd-port/bsd-port/hotspot: 5 new changesets
> | 1. It seems like something is wrong with the networking support using Zero.
> |    A test programme should be simple to construct, but I first noticed it
> |    trying to use a previously built JDK with Zero as the VM as a bootstrap:
> | 
> |    java.net.SocketException: Invalid argument
> |    at java.net.PlainSocketImpl.socketConnect(Native Method)
> |    at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:316)
> |    at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:177)
> |    at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:164)
> |    at java.net.Socket.connect(Socket.java:574)
> |    at java.net.Socket.connect(Socket.java:524)
> |    at sun.net.NetworkClient.doConnect(NetworkClient.java:174)
> |    ...
> | 
> |    when it tries to download the JAXP bundle.
> 
> sysctl -w net.inet6.ip6.v6only=0 ?

D'oh, yeah, I should have tried various options to force v4 only
networking.  I'll give that a shot later today.

> | 2. The sparc64 port is misbehaving a little.  I'm not sure yet if its
> |    something about sparc64 or if its because my sparc64 box is SMP.  I'll
> |    try a UP kernel to eliminate the latter.
> 
> Have not tried this yet.

I should elaborate on this a little more.  Most of the time the VM runs
fine.  However, disturbingly I will see sometimes see something like one
of these happen:

Exception in thread "Reference Handler"
java.lang.IllegalMonitorStateException
        at java.lang.Object.notifyAll(Native Method)
        at java.lang.ref.ReferenceQueue.enqueue(ReferenceQueue.java:68)
        at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:146)

-OR-

The process sits there basically idle and never completes.  Top shows it
in the state 'ucond'.

-OR-

The process crashes.  This is the rarest, but that isn't very comforting.  E.g.:

__sparc_utrap: fatal memory address not aligned
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  Internal Error (os_bsd_zero.cpp:232), pid=52706, tid=1097080192
#  Error: caught unhandled signal 4
#
# JRE version: 7.0
# Java VM: OpenJDK 64-Bit Zero VM (17.0-b05 interpreted mode bsd-sparc64 )
# An error report file with more information is saved as:
# /home/glewis/sparc64/OpenJDK7/bsd-port/jaxp/hs_err_pid52706.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#

Note that my bootstrapping procedure was somewhat convoluted, so I'm not
convinced the JDK I'm currently toying with is kosher.  I'm trying to use
it to build something I'm a little more confident in, so take the above
report with a grain of salt until then.

-- 
Greg Lewis                          Email   : glewis at eyesbeyond.com
Eyes Beyond                         Web     : http://www.eyesbeyond.com
Information Technology              FreeBSD : glewis at FreeBSD.org