From owner-freebsd-java@FreeBSD.ORG Mon Apr 24 13:32:08 2006 Return-Path: X-Original-To: freebsd-java@freebsd.org Delivered-To: freebsd-java@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C486A16A401 for ; Mon, 24 Apr 2006 13:32:08 +0000 (UTC) (envelope-from lists@intricatesoftware.com) Received: from mta2.srv.hcvlny.cv.net (mta2.srv.hcvlny.cv.net [167.206.4.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0726443D5C for ; Mon, 24 Apr 2006 13:32:07 +0000 (GMT) (envelope-from lists@intricatesoftware.com) Received: from [172.16.1.72] (ool-457a77e8.dyn.optonline.net [69.122.119.232]) by mta2.srv.hcvlny.cv.net (Sun Java System Messaging Server 6.2-4.03 (built Sep 22 2005)) with ESMTP id <0IY800J4EAWSOYWB@mta2.srv.hcvlny.cv.net> for freebsd-java@freebsd.org; Mon, 24 Apr 2006 09:31:40 -0400 (EDT) Date: Mon, 24 Apr 2006 09:31:39 -0400 From: Kurt Miller In-reply-to: <444A9253.4030309@fer.hr> To: freebsd-java@freebsd.org Message-id: <200604240931.40127.lists@intricatesoftware.com> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-2 Content-transfer-encoding: 7BIT Content-disposition: inline References: <4446398A.3020304@fer.hr> <200604191906.14542.lists@intricatesoftware.com> <444A9253.4030309@fer.hr> User-Agent: KMail/1.9.1 Subject: Re: Big problem with little java X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: kurt@intricatesoftware.com List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Apr 2006 13:32:08 -0000 On Saturday 22 April 2006 4:30 pm, Ivan Voras wrote: > Kurt Miller wrote: > > > Do you still have the crash logs around (i.e. hs_err_pidxxxxx.log)? > > Please post it to the list if you do. > > Yes, I have several; here they are: > http://geri.cc.fer.hr/~ivoras/stuff/hs_err_logs.tgz Thank you for making them available. The logs show that you are hitting the multiprocessor SIGBUS bug with diablo. The -XX:+UseMembar jvm argument is needed with diablo on multiprocessor systems to correct the problem. More details can be found in the archives in the "Diablo 1.5 SIGBUS - fixed" thread. -Kurt