From owner-freebsd-stable@FreeBSD.ORG Sat Mar 25 23:44:21 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD4E316A400 for ; Sat, 25 Mar 2006 23:44:21 +0000 (UTC) (envelope-from kreios@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id E83E043D5A for ; Sat, 25 Mar 2006 23:44:20 +0000 (GMT) (envelope-from kreios@gmail.com) Received: by wproxy.gmail.com with SMTP id 37so1215199wra for ; Sat, 25 Mar 2006 15:44:20 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=ZiyGpT1TE2ao0Y0S7C/Q5UGKWCsK9sSBQO257+yokaq/5IzN9uIRYo2M1K7Awl9MYN4Ipl5mg0IL27ZCRz3Y+HtbPAHMXRrP2QKRqStVw/cDCmWbA1onyKQESIg2sfkm0f/WfrZKzwQmstbckDPAoZIoch30wohdEJa3z+wrkWY= Received: by 10.65.53.10 with SMTP id f10mr1703717qbk; Sat, 25 Mar 2006 15:44:19 -0800 (PST) Received: by 10.64.91.6 with HTTP; Sat, 25 Mar 2006 15:44:19 -0800 (PST) Message-ID: <2de4f2a00603251544j55ceab65rb79ebeeb2859188a@mail.gmail.com> Date: Sat, 25 Mar 2006 17:44:19 -0600 From: kreios@gmail.com To: stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cc: Subject: Need help with isp driver and disk arrary X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Mar 2006 23:44:21 -0000 I am having a problem with the isp driver seeing a StorageTek disk array LUNs. I am directly attaching to the array and everything works find as long as I plug into the A controller on the array. When I connect up to the B controller, I can not see any of the LUNs advertised. The QLogic firmware can see the LUNs. The only difference I can see are that the LUNs start at 0 on the A side and at 3 on the B side. Kernel messages for the isp driver are: isp0: port 0xa000-0xa0ff mem 0xec060000-0xec060fff irq 17 at device 0.0 on pci1 isp0: Reserved 0x1000 bytes for rid 0x14 type 3 at 0xec060000 isp0: using Memory space register mapping isp0: [GIANT-LOCKED] isp0: Board Type 2312, Chip Revision 0x2, loaded F/W Revision 3.3.6 isp0: 839 max I/O commands supported isp0: NVRAM Port WWN 0x210000e08b1e4a71 isp0: bad execution throttle of 0- using 16 isp0: LIP Received isp0: Loop UP isp0: Port Database Changed isp0: LIP Received isp0: Port Database Changed isp0: Firmware State Ready> isp0: 2Gb link speed/s isp0: Loop ID 0, Port ID 0xef, Loop State 0x2, Topology 'Private Loop' isp0: Target 0 (Loop 0x0) Port ID 0xef (role Initiator) Arrived isp0: Target 2 (Loop 0x2) Port ID 0xe4 (role Target) Arrived camcontrol devlist -v shows the following when connected to port A: scbus0 on isp0 bus 0: at scbus0 target 0 lun 0 (da0,pass0) at scbus0 target 0 lun 1 (da1,pass1) at scbus0 target 0 lun 2 (da2,pass2) < > at scbus0 target -1 lun -1 () scbus-1 on xpt0 bus 0: < > at scbus-1 target -1 lun -1 (xpt0) camcontrol devlist -v shows the following when connected to port B: scbus0 on isp0 bus 0: < > at scbus0 target -1 lun -1 () scbus-1 on xpt0 bus 0: < > at scbus-1 target -1 lun -1 (xpt0) Thanks, -- Dave