From owner-freebsd-sparc64@FreeBSD.ORG Fri Nov 14 21:11:21 2008 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 73AE51065675 for ; Fri, 14 Nov 2008 21:11:21 +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 032938FC12 for ; Fri, 14 Nov 2008 21:11:20 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.3/8.14.3/ALCHEMY.FRANKEN.DE) with ESMTP id mAELBJJW012924; Fri, 14 Nov 2008 22:11:19 +0100 (CET) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.3/8.14.3/Submit) id mAELBJZW012923; Fri, 14 Nov 2008 22:11:19 +0100 (CET) (envelope-from marius) Date: Fri, 14 Nov 2008 22:11:19 +0100 From: Marius Strobl To: Mark Linimon Message-ID: <20081114211118.GG64456@alchemy.franken.de> References: <183638.12752.qm@web56802.mail.re3.yahoo.com> <20081031131827.GA9613@soaustin.net> <20081103223042.GB8256@alchemy.franken.de> <20081104115722.GA28394@soaustin.net> <20081104221003.GE31338@alchemy.franken.de> <20081105184746.GA26875@soaustin.net> <20081112201029.GE64456@alchemy.franken.de> <20081112213543.GA71577@alchemy.franken.de> <20081114161933.GA24688@soaustin.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081114161933.GA24688@soaustin.net> User-Agent: Mutt/1.4.2.3i Cc: freebsd-sparc64@freebsd.org Subject: Re: Free Ultra2 in Silicon Valley, USA 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: Fri, 14 Nov 2008 21:11:21 -0000 On Fri, Nov 14, 2008 at 10:19:33AM -0600, Mark Linimon wrote: > It turns out the T1-200s are much happier to boot if you actually > include the gem(4) driver in the kernel. > > Sigh. > > Anyways, thanks for the help investigating. > Ah, the problem then likely is that the GEMs are left initialized and running by the firmware; at some point, probably when some packet is received, the GEM DMAs something to a mapping the IOMMU no longer knows about since the kernel has taken it over and thus triggers a DMA error interrupt. If this happens when netbooting then it's probably time to fix libstand to no longer open and close the network device for every file access so we can remove the hack form the loader which just keeps the device open forever. On the other hand, it's probably beneficial in general to not remove the driver for the device one wants to netboot with :) Marius