From owner-freebsd-current@FreeBSD.ORG Sun Mar 18 23:55:03 2012 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 3952F106564A for ; Sun, 18 Mar 2012 23:55:03 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id DB3BF8FC12 for ; Sun, 18 Mar 2012 23:55:02 +0000 (UTC) Received: by vcmm1 with SMTP id m1so8173213vcm.13 for ; Sun, 18 Mar 2012 16:55:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=gkvVfHKSuypgf1h4LrjcbmG/tIT2bU5aJ44ddFkvm2o=; b=08SEy0QRbyg/bZ0F5tYnhH0YWfDNNwzMgrj0fmiGIWI02lxtpfT74MmmsItjc8IDHm K+GgGGJlvt7fTVk78ypHSBNTMAgnUlEzWIpBgFokMppQTqsAo5g0eyjm2DaOVplYPS1Q n8NMmTwUNkG3ru79GNsfyDZ5osGxSbowtr+3AwUfwJwcnHoaZizFd22tZZBNc1XRj4op rS6JYzwno4sKc+P/JvuqB17gYCJMo9bnR4lmwP4z4wJpU5JxcfCW7CW1lHiGkVwGewNG KgXZQix6q3suYJq69uFGoJrRLwvXEAA2ISNmenQ93uSLhfVjZ1MpDXnQShvo2ZgIo2Sd SZqA== MIME-Version: 1.0 Received: by 10.220.155.7 with SMTP id q7mr3800732vcw.71.1332114902101; Sun, 18 Mar 2012 16:55:02 -0700 (PDT) Received: by 10.220.2.130 with HTTP; Sun, 18 Mar 2012 16:55:02 -0700 (PDT) In-Reply-To: <4F666ABF.2090808@gmail.com> References: <4F666ABF.2090808@gmail.com> Date: Sun, 18 Mar 2012 16:55:02 -0700 Message-ID: From: Garrett Cooper To: deeptech71@gmail.com Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current@freebsd.org Subject: Re: port upgrade procedure is locked up X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Mar 2012 23:55:03 -0000 On Sun, Mar 18, 2012 at 4:07 PM, wrote: > A full port upgrade procedure seems to in some sort of a deadlock while > configuring a port. I did not try canceling and restarting the procedure, as > this may be a bug that should be fixed. If anyone wants to investigate, > quickly ask questions before these buggy video drivers decide to lock up as > usual. > > I generally don't have debugging symbols installed. Now I have an r233103 > world&kernel, and ~2.5 week old ports. talloc is the problem, not portupgrade. Look through the PR system and the archives for more details. Cheers, -Garrett