From owner-freebsd-scsi@FreeBSD.ORG Wed Feb 8 01:48:02 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 06DAD16A420 for ; Wed, 8 Feb 2006 01:48:02 +0000 (GMT) (envelope-from tspencer@hungry.com) Received: from terror.hungry.com (terror.hungry.com [199.181.107.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id B800743D48 for ; Wed, 8 Feb 2006 01:48:01 +0000 (GMT) (envelope-from tspencer@hungry.com) Received: from [10.251.17.233] (nat.ironport.com [63.251.108.100]) (AUTH: LOGIN tspencer, TLS: TLSv1/SSLv3,128bits,RC4-SHA) by terror.hungry.com with esmtp; Tue, 07 Feb 2006 17:48:01 -0800 Mime-Version: 1.0 (Apple Message framework v746.2) Content-Transfer-Encoding: 7bit Message-Id: <5EE96EFA-FF04-4542-A5BF-F60F2EA78D52@hungry.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-scsi@freebsd.org From: Tim Spencer Date: Tue, 7 Feb 2006 17:47:24 -0800 X-Mailer: Apple Mail (2.746.2) Subject: Speaking of Fibre-channel problems... 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: Wed, 08 Feb 2006 01:48:02 -0000 I've been using qlogic 2312 FC cards in my FreeBSD 4.11 hosts without problems (aside from lack of multipathing and so on :-), but when I tried to use them in a new AMD64 SMP FreeBSD 6.x host that I'm trying to qualify for our production environment, I'm having problems. The card doesn't seem to be able to join the fabric. The card's LEDs both light up while the system is booting, but after the isp driver initializes, it just goes to a yellow blinky light which I have come to associate with "I have not been initialized correctly". I turned on CAMDEBUG and hacked isp_prt to print everything out, and this is what I got during the boot up: ... (hundreds of repeats of the next 3 lines) Feb 7 17:02:25 Xsc-db3 kernel: isp0: RISC2HOST ISR 0x40000010 Feb 7 17:02:25 Xsc-db3 kernel: isp0: RISC2HOST ISR 0x40008010 Feb 7 17:02:25 Xsc-db3 kernel: isp0: usec1998392: 0xdcc880dc- >0xdcd86a92 enano 0x0000fe9b6 Feb 7 17:02:25 Xsc-db3 kernel: isp0: RISC2HOST ISR 0x40000010 Feb 7 17:02:25 Xsc-db3 kernel: isp0: RISC2HOST ISR 0x40008010 Feb 7 17:02:25 Xsc-db3 kernel: isp0: usec1999434: 0xdcde08dd- >0xdcede8c1 enano 0x0000fdfe4 Feb 7 17:02:25 Xsc-db3 kernel: isp0: kthread: FC state ungood Feb 7 17:02:25 Xsc-db3 kernel: isp0: kthread: waiting until called Feb 7 17:02:25 Xsc-db3 kernel: isp0: RISC2HOST ISR 0x40000010 Feb 7 17:02:25 Xsc-db3 kernel: acd0: CDROM at ata0-master UDMA33 Feb 7 17:02:25 Xsc-db3 kernel: isp0: isp_action code 4 Feb 7 17:02:25 Xsc-db3 last message repeated 4 times Feb 7 17:02:25 Xsc-db3 kernel: isp0: isp_action code 901 Feb 7 17:02:25 Xsc-db3 kernel: isp0: isp_action code 4 Feb 7 17:02:25 Xsc-db3 kernel: isp0: isp_action code 4 Feb 7 17:02:25 Xsc-db3 kernel: isp0: isp_action code 901 Feb 7 17:02:25 Xsc-db3 kernel: isp0: isp_action code 4 Feb 7 17:02:25 Xsc-db3 kernel: isp0: isp_action code 4 ... (hundreds of repeats of the previous 3 lines) Unfortunately, I don't have the start of all this, because it filled the dmesg space up and scrolled it off the top. Here's some more info on the system: : Xsc-db3.soma.ironport.com []#; uname -a FreeBSD Xsc-db3.soma.ironport.com 6.0-STABLE FreeBSD 6.0-STABLE #1: Tue Feb 7 16:47:28 PST 2006 root@Xsc-db3.soma.ironport.com:/usr/ obj/usr/src/sys/MESSAGING_GATEWAY.amd64_INSTALL amd64 : Xsc-db3.soma.ironport.com []#; I have this in MESSAGING_GATEWAY.amd64_INSTALL: # tspencer temporary hack options CAMDEBUG options CAM_DEBUG_BUS=-1 options CAM_DEBUG_TARGET=-1 options CAM_DEBUG_LUN=-1 # Qlogic FC card stuff device isp # Qlogic family device ispfw # Firmware for QLogic HBAs- normally a module Anyways, has anybody else solved this sort of problem? And if not, does anybody have any suggestions as to how to figure out what is going wrong? Thanks, and have fun! -tspencer