From owner-freebsd-sparc64@FreeBSD.ORG Tue May 28 23:36:06 2013 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 67899A2C for ; Tue, 28 May 2013 23:36:06 +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 028312D7 for ; Tue, 28 May 2013 23:36:05 +0000 (UTC) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.6/8.14.6/ALCHEMY.FRANKEN.DE) with ESMTP id r4SNYKq6085693; Wed, 29 May 2013 01:34:20 +0200 (CEST) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.6/8.14.6/Submit) id r4SNYKoI085692; Wed, 29 May 2013 01:34:20 +0200 (CEST) (envelope-from marius) Date: Wed, 29 May 2013 01:34:20 +0200 From: Marius Strobl To: Chris Ross Subject: Re: CAM timeouts on Netra X1 Message-ID: <20130528233420.GA85433@alchemy.franken.de> References: <20130325135951.GA45845@alchemy.franken.de> <20130325172203.GB955@alchemy.franken.de> <5F32C554-AE21-41AD-BE13-EA94BB0647CC@distal.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5F32C554-AE21-41AD-BE13-EA94BB0647CC@distal.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-sparc64@freebsd.org" X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 May 2013 23:36:06 -0000 On Mon, Mar 25, 2013 at 08:28:58PM -0400, Chris Ross wrote: > > On Mar 25, 2013, at 13:22 , Marius Strobl wrote: > > Urqs, I forgot the oddness of the (rather pointless) ata(4) module > > build. Either re-fetch the entire patch or just revert the changes > > to your local ata-all.h and then manually remove the prototype for > > ata_cam_begin_transaction() in it. > > Thanks. I had already re-updated my source tree so the patch was reverted, > and reapplying it caused a successful build, and I'm no longer seeing the > CAM timeouts. I am still loading the OS onto the disks [zfs pools], but I > think that's got it. > FYI, that fix was committed to head as r249199 and MFC'ed to stable/9 in r251081. Sorry for the delay. Marius