From owner-freebsd-sparc64@FreeBSD.ORG Tue Oct 5 18:56:29 2010 Return-Path: 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 072A51065696 for ; Tue, 5 Oct 2010 18:56:29 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) by mx1.freebsd.org (Postfix) with ESMTP id 92E598FC0A for ; Tue, 5 Oct 2010 18:56:28 +0000 (UTC) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.4/8.14.4/ALCHEMY.FRANKEN.DE) with ESMTP id o95IuOgO070409; Tue, 5 Oct 2010 20:56:24 +0200 (CEST) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.4/8.14.4/Submit) id o95IuOND070408; Tue, 5 Oct 2010 20:56:24 +0200 (CEST) (envelope-from marius) Date: Tue, 5 Oct 2010 20:56:24 +0200 From: Marius Strobl To: Nathaniel W Filardo Message-ID: <20101005185623.GA65846@alchemy.franken.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.4.2.3i 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Oct 2010 18:56:29 -0000 On Sun, Jul 25, 2010 at 10:32:52AM -0400, Nathaniel W Filardo wrote: > Hullo FBSD-sparc64, > > I'd like to report two issues, both conveniently occurring on new (to me), > uniprocessor hardware (so my gremlins of impossibilities past should > hopefully be banished) and within one core file. If I've left anything of > use out, please don't hesitate to ask. If I'm doing something dumb and > expecting it to work, don't hesitate to call me out on it. :) > > I built r210441+d769a9c with and without VIMAGE; with VIMAGE the system gets > as far through boot as enabling pf: FYI, if you where loading pf(4) as a module that hang likely is fixed with r212998. However, pf(4) hasn't been virtualized so far, so it won't work with VIMAGE anyway. Did you hit the "invalid pmap?" panic again with the patch for pmap_pinit() applied? Marius