From owner-freebsd-current@FreeBSD.ORG  Tue Oct 30 18:56:18 2007
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 6F7A416A41B
	for <freebsd-current@freebsd.org>; Tue, 30 Oct 2007 18:56:18 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Received: from weak.local (pointyhat.freebsd.org [IPv6:2001:4f8:fff6::2b])
	by mx1.freebsd.org (Postfix) with ESMTP id C186E13C4B7;
	Tue, 30 Oct 2007 18:56:17 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Message-ID: <47277E55.5060104@FreeBSD.org>
Date: Tue, 30 Oct 2007 19:56:21 +0100
From: Kris Kennaway <kris@FreeBSD.org>
User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728)
MIME-Version: 1.0
To: Christoph Friedrichs <christoph.friedrichs@helinet.de>
References: <47270246.4020400@helinet.de>
In-Reply-To: <47270246.4020400@helinet.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-current@freebsd.org
Subject: Re: Problem with libthr after update
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
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: Tue, 30 Oct 2007 18:56:18 -0000

Christoph Friedrichs wrote:
> Hi Guys,
> 
> I?m relatively new with my freebsd -current box and actual experiencing 
> problems with starting kdm and portupgrade. Everytime I do so the 
> kdm-bin log explodes with this error messages:
> 
> Fatal error 'Cannot allocate red zone for initial thread' at line 382 in 
> file /usr/src/lib/libthr/thread/thr_init.c (errno = 12)
> Fatal error 'Cannot allocate red zone for initial thread' at line 382 in 
> file /usr/src/lib/libthr/thread/thr_init.c (errno = 12)
> Fatal error 'Cannot allocate red zone for initial thread' at line 382 in 
> file /usr/src/lib/libthr/thread/thr_init.c (errno = 12)
> 
> I googled this problem and found something concering some ruby packages. 
> I did a manual rebuild of
> 
> ruby-1.8.6_2,1
> perl-5.8.8
> ruby18-bdb-0.6.2
> db41-4.1.25_4
> portupgrade-2.3.1,2
> 
> With this rebuild problems with portupgrade were solved but kdm keeps 
> refusing to start with same error messages. In UPDATING I found this:
> 
> 20071009:
>        Setting WITHOUT_LIBPTHREAD now means WITHOUT_LIBKSE and
>        WITHOUT_LIBTHR are set.
> 
> Does this probably have something to do with this?

Did you update from an older release of FreeBSD?

Kris