From owner-freebsd-current@FreeBSD.ORG Sun Jul 29 18:28:54 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 7BEA6106564A for ; Sun, 29 Jul 2012 18:28:54 +0000 (UTC) (envelope-from mj@feral.com) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.freebsd.org (Postfix) with ESMTP id 537018FC0C for ; Sun, 29 Jul 2012 18:28:54 +0000 (UTC) Received: from [192.168.135.103] (c-76-126-166-136.hsd1.ca.comcast.net [76.126.166.136]) (authenticated bits=0) by ns1.feral.com (8.14.4/8.14.4) with ESMTP id q6TISl2F075989 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Sun, 29 Jul 2012 11:28:48 -0700 (PDT) (envelope-from mj@feral.com) Message-ID: <501580DA.4060608@feral.com> Date: Sun, 29 Jul 2012 11:28:42 -0700 From: Matthew Jacob Organization: Feral Software User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <501575A0.2080007@protected-networks.net> In-Reply-To: <501575A0.2080007@protected-networks.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (ns1.feral.com [192.67.166.1]); Sun, 29 Jul 2012 11:28:48 -0700 (PDT) Subject: Re: post SVN r238886 no boot? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matt Jacob List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jul 2012 18:28:54 -0000 On 7/29/2012 10:40 AM, Michael Butler wrote: > Is anyone else having troubles getting -current after SVN r238886 to > boot? In my case, I have an unstoppable stream of pager_something > console messages :-( > > imb > me2 If I stop at single user and then continue, then all seems okay. I'm guessing (just a SWAG) that it might be related to the disk resize CAM stuff just added.