From owner-freebsd-ppc@FreeBSD.ORG Thu Aug 3 17:04:31 2006 Return-Path: X-Original-To: freebsd-ppc@freebsd.org Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9FC0416A4DE; Thu, 3 Aug 2006 17:04:31 +0000 (UTC) (envelope-from sobomax@sippysoft.com) Received: from sippysoft.com (gk.360sip.com [72.236.70.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A6F643D46; Thu, 3 Aug 2006 17:04:31 +0000 (GMT) (envelope-from sobomax@sippysoft.com) Received: from [192.168.1.56] ([204.244.149.125]) (authenticated bits=0) by sippysoft.com (8.13.6/8.13.6) with ESMTP id k73H4PEJ045006 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 3 Aug 2006 10:04:27 -0700 (PDT) (envelope-from sobomax@sippysoft.com) Message-ID: <44D22C7A.8030204@sippysoft.com> Date: Thu, 03 Aug 2006 10:03:54 -0700 From: Maxim Sobolev Organization: Sippy Software User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: Daniel Eischen References: <44D12AC0.90009@sippysoft.com> <0C6ADBC1-E3DF-47D1-AA77-EA9BD14E059F@xcllnt.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "current@freebsd.org" , freebsd-ppc@freebsd.org Subject: Re: Looks like threading is b0rken on FreeBSD/powerpc X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Aug 2006 17:04:31 -0000 Daniel Eischen wrote: > On Wed, 2 Aug 2006, Marcel Moolenaar wrote: > >> >> On Aug 2, 2006, at 3:44 PM, Maxim Sobolev wrote: >> >>> Hi, >>> >>> Apparently threading is b0rken on the FreeBSD/powerpc - csup(8) dumps >>> core with seg 11. The same csup(8) version compiled on 6.0 works just >>> fine on the same 7-CURRENT kernel. > > AFAIK, libpthread/KSE isn't quite there yet for powerpc. Do you have any idea about what's wrong with it? By the way, the same problem affects ia64 too (ia64/91846) and it has been working in 6.0 just file. Looks like it has something to do with the thread-local storage. -Maxim