From owner-freebsd-arm@FreeBSD.ORG Tue Feb 16 20:58:53 2010 Return-Path: Delivered-To: arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 62D2C106566C; Tue, 16 Feb 2010 20:58:53 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 18AB88FC0C; Tue, 16 Feb 2010 20:58:53 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.3/8.14.1) with ESMTP id o1GKsH2r034995; Tue, 16 Feb 2010 13:54:17 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Tue, 16 Feb 2010 13:54:30 -0700 (MST) Message-Id: <20100216.135430.702773873773944731.imp@bsdimp.com> To: stas@FreeBSD.org From: "M. Warner Losh" In-Reply-To: <20100216123646.fc741643.stas@FreeBSD.org> References: <20100215213907.GA43625@cicely7.cicely.de> <20100216183951.GI43625@cicely7.cicely.de> <20100216123646.fc741643.stas@FreeBSD.org> X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: arm@FreeBSD.org, ticso@cicely7.cicely.de, ticso@cicely.de, current@FreeBSD.org Subject: Re: bind fails with sig11 on start / pthread failure on ARM? X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Feb 2010 20:58:53 -0000 In message: <20100216123646.fc741643.stas@FreeBSD.org> Stanislav Sedov writes: : On Tue, 16 Feb 2010 19:39:51 +0100 : Bernd Walter mentioned: : : > : > Do we have a general threading problem on ARM? : > : : I don't think so. I used a lot of threaded applications on arm, and they : worked fine. However, this might be some obscure bug. I know that 6.x ARM worked with threads no problem. We had dozens of threads in our control programs. The one caveat is that I've found bugs in the atomic routines in the past, and have had people submit fixes as well. All of those should be in the tree, but since some arrived when I was crazy busy for Cisco, they might have fallen on the floor. Warner