From owner-freebsd-questions@FreeBSD.ORG Sun Oct 5 18:19:04 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7FF64106568A for ; Sun, 5 Oct 2008 18:19:04 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from mail.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id 4862A8FC25 for ; Sun, 5 Oct 2008 18:19:03 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from localhost (mail.rachie.is-a-geek.net [192.168.2.101]) by mail.rachie.is-a-geek.net (Postfix) with ESMTP id 04B23AFBC01; Sun, 5 Oct 2008 10:19:03 -0800 (AKDT) From: Mel To: freebsd-questions@freebsd.org Date: Sun, 5 Oct 2008 20:19:01 +0200 User-Agent: KMail/1.9.7 References: <86r66v6gsj.fsf@ponoka.ab.hsia.telus.net> <200810051546.28440.fbsd.questions@rachie.is-a-geek.net> <86bpxz58l9.fsf@ponoka.ab.hsia.telus.net> In-Reply-To: <86bpxz58l9.fsf@ponoka.ab.hsia.telus.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200810052019.01920.fbsd.questions@rachie.is-a-geek.net> Cc: db@freebsd.org, Dale Hagglund Subject: Re: processes hanging in _umtx_op X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Oct 2008 18:19:04 -0000 On Sunday 05 October 2008 18:07:30 Dale Hagglund wrote: > >>>>> "Mel" == Mel writes: > Mel> It's not a 'standard answer', btw, but an educated guess, since > Mel> utmx is (simplified) the kernel equivalent of > Mel> pthread_(rwlock|mutex)_* and looks like it's hanging in one of > Mel> those functions. > > This was my guess as well. I first noticed this hang while attempting > to build gnuradio around the end of August. During conversations with > the maintainer, Diane Bruce, about this hang she recognized it from > before and suggested that she'd been able to fix it at that time by > upgrading all ports (or maybe just the wx port) on her system. > > Mel> Now, it can simply be programmer error (lock twice, unlock > Mel> once), but most of the time the kernel catches this for me with > Mel> EDEADLK. > > The background with gnuradio and the Diane's suggestion to upgrade ports > lead to my thought that I could easily have some sort of conflicting or > out-of-date combination of libraries causing some sort of locking > problem. If upgrading ports is a possible solution, then you have the fine task of finding out, which library in everything that's being loaded is *NOT* linked with libthr, cause a likely candidate would be two different threading libraries being used. I would start with ldd -a /path/to/python/wx.so and see if both libthr.so and libpthread.so (or maybe even libkse) show up. Also inspect /etc/libmap.conf for entries you may have added in a not too recent past and forgot about. Unfortunately, I see no obvious candidates in your package list (ie: compat-[456]x, *flash*). -- Mel Problem with today's modular software: they start with the modules and never get to the software part.