From owner-freebsd-current@FreeBSD.ORG  Fri Aug  5 15:47:39 2011
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.org
Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28])
	by hub.freebsd.org (Postfix) with ESMTP id 33143106567D;
	Fri,  5 Aug 2011 15:47:39 +0000 (UTC)
	(envelope-from jkim@FreeBSD.org)
From: Jung-uk Kim <jkim@FreeBSD.org>
To: freebsd-current@FreeBSD.org
Date: Fri, 5 Aug 2011 11:47:29 -0400
User-Agent: KMail/1.6.2
References: <E1QpFqI-0000iV-Pk@clue.co.za>
	<201108051142.17943.jkim@FreeBSD.org>
In-Reply-To: <201108051142.17943.jkim@FreeBSD.org>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201108051147.31658.jkim@FreeBSD.org>
Cc: Ian FREISLICH <ianf@clue.co.za>
Subject: Re: fdescfs mount causes hard lock
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Aug 2011 15:47:39 -0000

On Friday 05 August 2011 11:41 am, Jung-uk Kim wrote:
> On Friday 05 August 2011 04:33 am, Ian FREISLICH wrote:
> > Hi
> >
> > Since CURRENT Aug 2, my machine has hardlocked at boot time on
> > "Mounting local filesystems".  I traced it this morning to
> >
> > fdesc          /dev/fd         fdescfs         rw      0       0
> >
> > Not mounting this stopped the hardlock.  I added it because one
> > installed port requeried it, but I can't remember which port that
> > was.
> >
> > Is this related to the panic recently reported by David
> > Wolfskill?
>
> Yes, reverting r224614 fixed the hang for me.  Alternatively,
> please try the last patch posted in the thread.

Actually, this patch was committed as r224655, it seems. :-)

Jung-uk Kim