From owner-freebsd-ports@FreeBSD.ORG Mon Jul 12 17:36:55 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A69C716A4CE for ; Mon, 12 Jul 2004 17:36:55 +0000 (GMT) Received: from infoline.su (delta.infoline.su [194.135.56.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8860943D39 for ; Mon, 12 Jul 2004 17:36:54 +0000 (GMT) (envelope-from nevis2us@infoline.su) Received: from baikal.home.test ([217.150.202.99]) by infoline.su (infoline.su [194.135.56.4]) (MDaemon.PRO.v6.8.5.R) with ESMTP id 3-md50000000056.tmp for ; Mon, 12 Jul 2004 21:35:58 +0400 Received: from [10.0.0.1] (baikal.home.test [10.0.0.1]) by baikal.home.test (8.12.11/8.12.11) with ESMTP id i6B8JLaj032872 for ; Sun, 11 Jul 2004 12:19:22 +0400 (MSD) (envelope-from nevis2us@infoline.su) Message-ID: <40F0F808.1000906@infoline.su> Date: Sun, 11 Jul 2004 12:19:20 +0400 From: Alexander Kirillov User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7) Gecko/20040629 X-Accept-Language: ru, en, en-us MIME-Version: 1.0 To: freebsd-ports@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Processed: infoline.su, Mon, 12 Jul 2004 21:35:58 +0400 (not processed: message from valid local sender) X-MDRemoteIP: 217.150.202.99 X-Return-Path: nevis2us@infoline.su X-MDaemon-Deliver-To: freebsd-ports@freebsd.org Subject: Re: mozilla-1.7,2 and jdk-1.4.2p6_4 plugin problem X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: nevis2us@infoline.su List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jul 2004 17:36:55 -0000 Yep. This is it. It works after I added /dev/psm0 as an entropy source. Tried this after exhausting entropy pool with cat /dev/urandom and with/without ps2 mouse irq added. Got consistent results. Thanks for your help Greg! Sasha >>More info on the problem. >>Looking at the thread stack dumps when the browser gets stuck >>I've found threads locked within sun.security.provider.SeedGenerator >>methods. >> >>The reason why I'm having trouble loading applets over http is that >>I have grant codeBase "https://something/-" in my ~/.java.policy file. >>As soon as I removed https:// clause from my ~/.java.policy everything >>works fine over http. >> >>I've attached thread stack dump at the end of the message. >>Hope this may help to reproduce and fix the problem. > > > Ok, I've got a good guess now. The stack trace suggests that the JVM > is stuck trying to read secure random bytes from /dev/random. This is > a fairly common problem (particularly on 4.x) if the random device > isn't hooked up to enough entropy sources to gather "randomness" from. > Try using rndcontrol(8) to provide yourself with some more entropy > sources and let me know if that resolves the problem. There are some > pointers on doing this in the freebsd-java mailing list archives. >