From: Anton Blanchard <anton@samba.org>
To: Andrew Vasquez <andrew.vasquez@qlogic.com>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
Andrew Morton <akpm@osdl.org>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH] qla2xxx - perform proper SNS scans with ISP2200 HBAs.
Date: Fri, 23 Jan 2004 11:18:17 +1100 [thread overview]
Message-ID: <20040123001817.GG11236@krispykreme> (raw)
In-Reply-To: <B179AE41C1147041AA1121F44614F0B0598E53@AVEXCH02.qlogic.org>
Hi Andrew,
> The 2200 firmware doesn't support the MS IOCB interface the driver
> uses to issue CT commands to the SNS. Basically, I had to
> forward-port some code from the 6.x driver to get the SNS calls
> to go through. I've had several machines (mixture of 2200s/
> 2300s/others with loop and fabric connections) running with this
> patch for the past few days.
I applied your patch to 2.6.2-rc1 and tested it on my ppc64 box. Looks
like its not happy :) Maybe a 64bit or big endian issue?
Anton
QLogic ISP2xxx PCI/PCI-X Fibre Channel HBA Driver (c00000000063a028)
PCI: Enabling device: (0003:41:01.0), cmd 143
qla2200 0003:41:01.0: Found an ISP2200, irq 183, iobase 0xa000000080020000
qla2200 0003:41:01.0: Configuring PCI space...
qla2200 0003:41:01.0: Configure NVRAM parameters...
qla2200 0003:41:01.0: Verifying loaded RISC code...
qla2200 0003:41:01.0: LIP reset occured (0).
qla2200 0003:41:01.0: Waiting for LIP to complete...
qla2200 0003:41:01.0: LOOP UP detected (1 Gbps).
qla2200 0003:41:01.0: Topology - (F_Port), Host Loop address 0xffff
scsi0 : qla2xxx
qla2200 0003:41:01.0:
QLogic ISP2xxx PCI/PCI-X Fibre Channel HBA Driver: 8.00.00b8
QLogic QLA22xx -
ISP2200: PCI (66 MHz) @ 0003:41:01.0 hdma-, host#=0, fw=2.02.06 TP
qla2200 0003:41:01.0: Invalid ISP SCSI completion handle
qla2200 0003:41:01.0: Performing ISP error recovery - ha= c00000000fd202e0.
qla2200 0003:41:01.0: LIP reset occured (0).
qla2200 0003:41:01.0: LOOP UP detected (1 Gbps).
qla2200 0003:41:01.0: Invalid ISP SCSI completion handle
qla2200 0003:41:01.0: Performing ISP error recovery - ha= c00000000fd202e0.
qla2200 0003:41:01.0: LIP reset occured (f7f7).
qla2200 0003:41:01.0: LOOP UP detected (1 Gbps).
qla2200 0003:41:01.0: Invalid ISP SCSI completion handle
qla2200 0003:41:01.0: Performing ISP error recovery - ha= c00000000fd202e0.
qla2200 0003:41:01.0: LIP reset occured (f7f7).
qla2200 0003:41:01.0: LOOP UP detected (1 Gbps).
qla2200 0003:41:01.0: Invalid ISP SCSI completion handle
qla2200 0003:41:01.0: Performing ISP error recovery - ha= c00000000fd202e0.
qla2200 0003:41:01.0: LIP reset occured (f7f7).
qla2200 0003:41:01.0: LOOP UP detected (1 Gbps).
qla2200 0003:41:01.0: Invalid ISP SCSI completion handle
qla2200 0003:41:01.0: Performing ISP error recovery - ha= c00000000fd202e0.
qla2200 0003:41:01.0: LIP reset occured (f7f7).
qla2200 0003:41:01.0: LOOP UP detected (1 Gbps).
qla2200 0003:41:01.0: Invalid ISP SCSI completion handle
qla2200 0003:41:01.0: Performing ISP error recovery - ha= c00000000fd202e0.
qla2200 0003:41:01.0: LIP reset occured (f7f7).
qla2200 0003:41:01.0: LOOP UP detected (1 Gbps).
qla2200 0003:41:01.0: Invalid ISP SCSI completion handle
qla2200 0003:41:01.0: Performing ISP error recovery - ha= c00000000fd202e0.
qla2200 0003:41:01.0: LIP reset occured (f7f7).
qla2200 0003:41:01.0: LOOP UP detected (1 Gbps).
qla2200 0003:41:01.0: Invalid ISP SCSI completion handle
qla2200 0003:41:01.0: Performing ISP error recovery - ha= c00000000fd202e0.
qla2200 0003:41:01.0: LIP reset occured (f7f7).
qla2200 0003:41:01.0: LOOP UP detected (1 Gbps).
qla2200 0003:41:01.0: Invalid ISP SCSI completion handle
qla2200 0003:41:01.0: Performing ISP error recovery - ha= c00000000fd202e0.
qla2200 0003:41:01.0: LIP reset occured (f7f7).
qla2200 0003:41:01.0: LOOP UP detected (1 Gbps).
qla2200 0003:41:01.0: Invalid ISP SCSI completion handle
qla2200 0003:41:01.0: Performing ISP error recovery - ha= c00000000fd202e0.
qla2200 0003:41:01.0: LIP reset occured (f7f7).
qla2200 0003:41:01.0: LOOP UP detected (1 Gbps).
next prev parent reply other threads:[~2004-01-23 0:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 17:12 [PATCH] qla2xxx - perform proper SNS scans with ISP2200 HBAs Andrew Vasquez
2004-01-23 0:18 ` Anton Blanchard [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-23 0:49 Andrew Vasquez
2004-01-23 1:18 ` Anton Blanchard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040123001817.GG11236@krispykreme \
--to=anton@samba.org \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=andrew.vasquez@qlogic.com \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox