From owner-freebsd-current@FreeBSD.ORG Mon Oct 15 12:57:10 2007 Return-Path: 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 A8FA116A41A for ; Mon, 15 Oct 2007 12:57:10 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id 71D4613C474 for ; Mon, 15 Oct 2007 12:57:10 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.1/8.14.1/NETPLEX) with ESMTP id l9FCv1Pj013447; Mon, 15 Oct 2007 08:57:01 -0400 (EDT) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-3.0 (mail.netplex.net [204.213.176.10]); Mon, 15 Oct 2007 08:57:01 -0400 (EDT) Date: Mon, 15 Oct 2007 08:57:01 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: oleg palukhin In-Reply-To: <47134F8A.4030309@electro-mpo.ru> Message-ID: References: <47134F8A.4030309@electro-mpo.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: error with thread X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Oct 2007 12:57:10 -0000 On Mon, 15 Oct 2007, oleg palukhin wrote: > hi, list > > on recently builded -current when i start X, portupgrade and some else > programms I get a lot of this error: > "Fatal error 'Cannot allocate red zone for initial thread' at line 382 > in file /usr/src/lib/libthr/thread/thr_init.c (errno = 12)", and coredump > then. > > googlin' give me feeling that it's good known sort of issue, but I couldn't > find any example of soving > > just where to look to solve it? Try manually rebuilding portupgrade and the ports that depend on it. My -current ports are old, but do something like this: # pkg_which /usr/local/sbin/portupgrade portupgrade-devel-2.3.0_5 # pkg_info -r portupgrade-devel-2.3.0_5 Information for portupgrade-devel-2.3.0_5: Depends on: Dependency: db41-4.1.25_4 Dependency: ruby-1.8.6,1 Dependency: perl-5.8.8 Dependency: ruby18-bdb-0.6.0 # pkg_info -oq db41-4.1.25_4 ruby-1.8.6,1 perl-5.8.8 ruby18-bdb-0.6.0 databases/db41 lang/perl5.8 lang/ruby18 databases/ruby-bdb So you'd rebuild those 4 ports and ports-mgmt/portupgrade. According to a recent post, you might only need to rebuild the ruby related ports and portupgrade. Disclaimer: I have not gone through this, just reiterating what I saw in a recent post. -- DE