From owner-freebsd-sparc64@FreeBSD.ORG  Sun Jul 25 20:01:14 2010
Return-Path: <owner-freebsd-sparc64@FreeBSD.ORG>
Delivered-To: freebsd-sparc64@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 862FE106566C
	for <freebsd-sparc64@freebsd.org>; Sun, 25 Jul 2010 20:01:14 +0000 (UTC)
	(envelope-from mmoll@darkthrone.kvedulv.de)
Received: from darkthrone.kvedulv.de (darkthrone.kvedulv.de
	[IPv6:2001:1578:400:101::2])
	by mx1.freebsd.org (Postfix) with ESMTP id 2531B8FC19
	for <freebsd-sparc64@freebsd.org>; Sun, 25 Jul 2010 20:01:13 +0000 (UTC)
Received: by darkthrone.kvedulv.de (Postfix, from userid 666)
	id A2D051CC9C; Sun, 25 Jul 2010 22:01:11 +0200 (CEST)
Date: Sun, 25 Jul 2010 22:01:11 +0200
From: Michael Moll <kvedulv@kvedulv.de>
To: Nathaniel W Filardo <nwf@cs.jhu.edu>
Message-ID: <20100725200111.GA22425@darkthrone.kvedulv.de>
References: <20100725143252.GV21929@gradx.cs.jhu.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20100725143252.GV21929@gradx.cs.jhu.edu>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: freebsd-sparc64@freebsd.org
Subject: Re: VIMAGE hang, USB panic
X-BeenThere: freebsd-sparc64@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting FreeBSD to the Sparc <freebsd-sparc64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>, 
	<mailto:freebsd-sparc64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-sparc64>
List-Post: <mailto:freebsd-sparc64@freebsd.org>
List-Help: <mailto:freebsd-sparc64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>,
	<mailto:freebsd-sparc64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Jul 2010 20:01:14 -0000

Hi,

On Sun, Jul 25, 2010 at 10:32:52AM -0400, Nathaniel W Filardo wrote:
> I built r210441+d769a9c with and without VIMAGE; with VIMAGE the system gets
> as far through boot as enabling pf:
> 
> > Starting pflog.
> > pflog0: promiscuous mode eEnabling pfnabled
> > Jul 25 09:12:06 pflogd[1883]: [priv]: msg PRIV_OPEN_LOG received
> 
> and then seems to hang forever;

I'm facing a somewhat similar problem (kern/147769). A workaround is
to compile if_epair statically into the kernel. You could try to add
device pf
device pflog
to your kernel configuration and see what happens.

If that doesn't work, add
options	KDB
options	DDB
options BREAK_TO_DEBUGGER
to your kernel configuration, then you can send a break signal and
generate a backtrace and/or dump for further analysis at the debugger.

Kind Regards
-- 
Michael Moll