From owner-freebsd-sparc64@FreeBSD.ORG Tue Mar 26 00:29:03 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 3E375CCE for ; Tue, 26 Mar 2013 00:29:03 +0000 (UTC) (envelope-from cross+freebsd@distal.com) Received: from mail.distal.com (mail.distal.com [IPv6:2001:470:e24c:200::ae25]) by mx1.freebsd.org (Postfix) with ESMTP id 15A1CBFD for ; Tue, 26 Mar 2013 00:29:02 +0000 (UTC) Received: from magrathea.distal.com (magrathea.distal.com [IPv6:2001:470:e24c:200:ea06:88ff:feca:960e]) (authenticated bits=0) by mail.distal.com (8.14.3/8.14.3) with ESMTP id r2Q0SwRp003470 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 25 Mar 2013 20:28:58 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Subject: Re: CAM timeouts on Netra X1 From: Chris Ross In-Reply-To: <20130325172203.GB955@alchemy.franken.de> Date: Mon, 25 Mar 2013 20:28:58 -0400 Content-Transfer-Encoding: 7bit Message-Id: <5F32C554-AE21-41AD-BE13-EA94BB0647CC@distal.com> References: <20130325135951.GA45845@alchemy.franken.de> <20130325172203.GB955@alchemy.franken.de> To: Marius Strobl X-Mailer: Apple Mail (2.1503) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.2 (mail.distal.com [IPv6:2001:470:e24c:200::ae25]); Mon, 25 Mar 2013 20:28:59 -0400 (EDT) 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, 26 Mar 2013 00:29:03 -0000 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. Thanks! - Chris