From owner-freebsd-scsi@FreeBSD.ORG Thu May 3 16:58:44 2012 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C06831065670 for ; Thu, 3 May 2012 16:58:44 +0000 (UTC) (envelope-from trent@snakebite.org) Received: from exchange.liveoffice.com (exchla3.liveoffice.com [64.70.67.188]) by mx1.freebsd.org (Postfix) with ESMTP id 9B8C18FC0C for ; Thu, 3 May 2012 16:58:44 +0000 (UTC) Received: from EXHUB03.exchhosting.com (192.168.11.104) by exhub14.exchhosting.com (192.168.11.123) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 3 May 2012 09:58:44 -0700 Received: from EXMBX10.exchhosting.com ([fe80::9c37:32f6:a508:a44f]) by EXHUB03.exchhosting.com ([fe80::ac41:fbe5:3959:ad64%12]) with mapi; Thu, 3 May 2012 09:58:43 -0700 From: Trent Nelson To: "mj@feral.com" Date: Thu, 3 May 2012 09:58:40 -0700 Thread-Topic: Missing sysctl options for isp driver Thread-Index: Ac0pTf75NPJ/UMmTRoqq9owxmKGvww== Message-ID: <3B12476E-569B-415D-9F2A-BF67652BB518@snakebite.org> References: <20120502203948.GA1141@snakebite.org> <4FA1DF1C.2030706@feral.com> <20120503050956.GA18983@snakebite.org> <4FA28976.2070607@feral.com> In-Reply-To: <4FA28976.2070607@feral.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-scsi@freebsd.org" Subject: Re: Missing sysctl options for isp driver X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 May 2012 16:58:44 -0000 >> (da37:isp1:0:88:0): got CAM status 0x4a >> (da37:isp1:0:88:0): fatal error, failed to attach to device >> (da37:isp1:0:88:0): removing device entry >> (da2:isp0:0:9:0): Synchronize cache failed, status =3D=3D 0x1b, scsi sta= tus =3D=3D 0x0 >> (da38:isp1:0:102:0): got CAM status 0x4a >> (da38:isp1:0:102:0): fatal error, failed to attach to device >> (da38:isp1:0:102:0): removing device entry >> isp0: Chan 0 PLOGI 0x020500 failed >> isp0: Chan 0 PLOGI 0x020600 failed >> isp0: Chan 0 PLOGI 0x020800 failed >> isp0: Mailbox Command 'BUS RESET' failed (COMMAND ERROR) >> isp1: Mailbox Command 'BUS RESET' failed (COMMAND ERROR) >> (da119:isp1:0:3:0): lost device - 0 outstanding, 0 refs >> (da119:isp1:0:3:0): removing device entry >> isp1: Chan 0 PLOGI 0x0201ca failed >> isp1: Chan 0 PLOGI 0x0201cb failed >> isp0: Chan 0 PLOGI 0x0101e0 failed >> isp0: Chan 0 PLOGI 0x0101e1 failed >> isp0: Chan 0 PortID 0x0102ad already at 512 handle 35 state 5 >> isp0: Chan 0 PortID 0x0102ae already at 512 handle 34 state 5 >> isp0: Chan 0 PortID 0x0102b1 already at 512 handle 33 state 5 >> isp0: Chan 0 PortID 0x0102b2 already at 512 handle 32 state 5 >> isp0: Chan 0 PortID 0x0102b3 already at 512 handle 31 state 5 >>=20 >> If I plug the HBA directly into a port on the JBOD, I get no such is= sues; >> all /dev/da* device nodes are created instantly and everything just = seems >> to work. (I presume HBA->JBOD would result in an FC-AL topology rat= her >> than an F-port topology, which I figure translates into a different = code >> path in the isp driver.) >>=20 >> When I enabled zoning and configured a HBA to only see a handful of = disks, >> everything behaved properly. I'm going to update to head and get a = debug >> build going with all the ISP debug bells and whistles; I'll report b= ack on >> HBA->fabric behaviour when zoning is off after that. >>=20 >> (FWIW, I've got two HP-UX (PA-RISC and IA64) boxes with two HBAs als= o >> plugged into the fabric; they don't go into fits like FreeBSD/isp se= ems >> to when zoning is turned off.) >>=20 >=20 > What kind of switches are you using? This is definitely wrong, and=20 > probably means that I need to do some work again here. They're Brocade Silkworms (3000 model?) branded by HP/Compaq as "HP Storage= Works SAN Switch 2/16". Both switches are running Brocade's Fabric OS v3.2= .1c, which is basically the latest (and last) firmware issued in the 3.x se= ries. The 4.x firmware/OS only runs on newer hardware. I got my main boxes to netboot off a head debug build before leaving the la= b, I'll try and replicate the nutty-behaviour-when-unzoned over the next co= uple of days and get a bit more info for you. (You're more than welcome to= full access to the network if it helps debugging/testing things.) Trent.