From owner-freebsd-java@FreeBSD.ORG Wed May 3 16:43:25 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 EFCB816A402 for ; Wed, 3 May 2006 16:43:25 +0000 (UTC) (envelope-from glewis@eyesbeyond.com) Received: from misty.eyesbeyond.com (gerbercreations.com [71.39.140.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 559DF43D45 for ; Wed, 3 May 2006 16:43:25 +0000 (GMT) (envelope-from glewis@eyesbeyond.com) Received: from misty.eyesbeyond.com (localhost.eyesbeyond.com [127.0.0.1]) by misty.eyesbeyond.com (8.13.3/8.13.3) with ESMTP id k43GhNL3038165; Wed, 3 May 2006 09:43:24 -0700 (PDT) (envelope-from glewis@eyesbeyond.com) Received: (from glewis@localhost) by misty.eyesbeyond.com (8.13.3/8.13.3/Submit) id k43GhNiO038164; Wed, 3 May 2006 09:43:23 -0700 (PDT) (envelope-from glewis@eyesbeyond.com) X-Authentication-Warning: misty.eyesbeyond.com: glewis set sender to glewis@eyesbeyond.com using -f Date: Wed, 3 May 2006 09:43:23 -0700 From: Greg Lewis To: Richard Cooper Message-ID: <20060503164323.GD37932@misty.eyesbeyond.com> References: <4458C430.9060005@jonnycalcutta.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4458C430.9060005@jonnycalcutta.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-java@FreeBSD.org Subject: Re: Diablo 1.5 SIGBUS X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 16:43:26 -0000 On Wed, May 03, 2006 at 03:54:40PM +0100, Richard Cooper wrote: > I'm running tomcat on FreeBSD 6.1-RC with diablo -1.5.0.06.00 (this is > the current port as of today). This is on an amd64 X2 with SMP running. > > I am getting the SIGBUS error that was mentioned back in April - > > > I was able to catch the SIGBUS in gdb once so far on a remote > > multiprocessor system. There was some evidence that the use of > > of the jvm argument -XX:+UseMembar will help correct the problem. > > I wasn't readily able to reproduce the problem so I'm not sure > > yet if this is the proper solution. Can those of you who are > > getting the SIGBUS try this and see if it improves things? > > It seems the problem has some kind of temporary fix at least. _My_ > problem is I am no developer (bash and cgi are about my limits - I'm > setting up a load test machine for tomcat developers). So if someone > could be kind enough to give me a quick step by step on how to execute > this solution I would be eternally grateful. I've looked in > /usr/local/bin/javavm, as it was suggested adding the above fix there, > but I wouldn't even know where to start. You did say bash was within your limits, and javavm is a shell script... :) A quick and dirty hack would involve something like this. Every where it invokes tryJavaCommand (there are about 6 instances) you need to add -XX:+UseMembar. That is, the lines look something like: tryJavaCommand "PATH_TO_JAVA_COMMAND" "${@}" make them tryJavaCommand "PATH_TO_JAVA_COMMAND" -XX:+UseMembar "${@}" You don't really need to change all six instances, but which to change depends on your usage pattern, so changing all 6 is safe. If that works you owe me two beers... ;) -- Greg Lewis Email : glewis@eyesbeyond.com Eyes Beyond Web : http://www.eyesbeyond.com Information Technology FreeBSD : glewis@FreeBSD.org