From owner-freebsd-current@FreeBSD.ORG  Wed Feb  4 17:07:07 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id CE9B916A4CE
	for <current@freebsd.org>; Wed,  4 Feb 2004 17:07:07 -0800 (PST)
Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6705043D55
	for <current@freebsd.org>; Wed,  4 Feb 2004 17:07:06 -0800 (PST)
	(envelope-from eischen@vigrid.com)
Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4])
	by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id i15175fo024701;
	Wed, 4 Feb 2004 20:07:05 -0500 (EST)
Date: Wed, 4 Feb 2004 20:07:05 -0500 (EST)
From: Daniel Eischen <eischen@vigrid.com>
X-Sender: eischen@pcnet5.pcnet.com
To: Wiktor Niesiobedzki <bsd@w.evip.pl>
In-Reply-To: <20040204231204.GO43404@mail.evip.pl>
Message-ID: <Pine.GSO.4.10.10402042006020.22525-100000@pcnet5.pcnet.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: current@freebsd.org
Subject: Re: libpthread: Fatal error 'Thread is not system scope'
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Feb 2004 01:07:07 -0000

On Thu, 5 Feb 2004, Wiktor Niesiobedzki wrote:

> Hi,
> 
> After some longer work with threaded Java application I got following error:
> Fatal error 'Thread is not system scope.
> ' at line 320 in file /usr/src/lib/libpthread/thread/thr_sig.c (errno = 2)
> Fatal error 'mutex is on list' at line 516 in file
> /usr/src/lib/libpthread/thread/thr_mutex.c (errno = 2)
> 
> I use jdk1.4.2 linked against libc_r, libmaped to libpthread
> 
> After that one of the thread started to consume 100% of CPU, and ktrace
> showed:
> 20906 java     CALL  kse_release(0x8056fb4)
> 20906 java     RET   kse_release -1 errno 22 Invalid argument
> 20906 java     CALL  kse_release(0x8056fb4)
> [...]
> 
> 
> It is not the first time, this error occures, but it takes time, to trigger
> it.
> 
> Is there any more info I may provide you?

Usually, this is because you are using something which stomps
on %gs.  And usually, this is Nvidia drivers/libraries.  Check
kernel messages for static ldt warnings.  If you have any,
that is the problem.

-- 
Dan Eischen