From: Andrew Vasquez <praka@users.sourceforge.net>
To: linux-scsi@vger.kernel.org
Subject: Re: Removing the qlogicfc driver
Date: Sat, 17 Jan 2004 12:21:07 -0800 [thread overview]
Message-ID: <20040117202107.GA8301@praka.local.home> (raw)
In-Reply-To: <200401171357.54813.christophe.varoqui@free.fr>
On Sat, 17 Jan 2004, christophe.varoqui wrote:
> On Friday 16 January 2004 23:57, Andrew Vasquez wrote:
>
> > Hmm, from the output of proc/scsi/qla* your two 2200 don't appear to
> > be recognizing any devices after the SNS scan:
> > Could you enable enable a couple of debug swtiches:
> > Andrew Vasquez
>
> Yes, here it is :
>
[snip]
> scsi(4): Asynchronous PORT UPDATE.
> scsi(4): Port database changed 0000 4000.
> scsi(4): F/W Ready - OK
> scsi(4): fw_state=3 curr time=4926cc4.
Firmware appears to be ready.
> qla2200 0000:03:01.0: Topology - (F_Port), Host Loop address 0xffff
F_PORT connection to the switch, we should have a PortID.
> scsi(4): Configure loop -- dpc flags =0x80040
> scsi(4): RSCN queue entry[0] = [00/000000].
> scsi(4): device_resync: rscn overflow.
> qla2x00_mailbox_command(4): **** FAILED. mbx0=4005, mbx1=0, mbx2=3c, cmd=54
> ****
> qla2x00_issue_iocb(4): failed rval 0x102qla2x00_issue_iocb(4): failed rval
> 0x102scsi(4): RFT_ID issue IOCB failed (258).
[snip]
> qla2x00_issue_iocb(4): failed rval 0x102qla2x00_issue_iocb(4): failed rval
> 0x102scsi(4): GA_NXT issue IOCB failed (258).
> scsi(4): Configure fabric error exit: rval=258
>
Yet it seems all of our SNS commands are failing to be executed with a
4005 (command error). Interesting, I'll need to talk with the
firmware folks on Monday.
In the interim, after the 8.x series driver is loaded, could you use
the switch software to take a look at the name-server's list of
recognized devices. I'm interested to know the information (port_id,
nn, pn, etc) it has related to the ports of the 2200s (from a previous
email, 210000e08b03896a).
Regards,
Andrew Vasquez
next prev parent reply other threads:[~2004-01-17 20:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <B179AE41C1147041AA1121F44614F0B0598E38@AVEXCH02.qlogic.org>
2004-01-17 12:57 ` Removing the qlogicfc driver christophe.varoqui
2004-01-17 20:21 ` Andrew Vasquez [this message]
2004-01-18 21:14 ` christophe.varoqui
2004-01-20 0:46 Andrew Vasquez
2004-01-20 13:42 ` christophe.varoqui
2004-02-01 16:09 ` Christoph Hellwig
2004-02-01 16:52 ` christophe varoqui
-- strict thread matches above, loose matches on Subject: below --
2004-01-19 17:28 Andrew Vasquez
2004-01-16 22:18 christophe.varoqui
2004-01-16 16:49 James Bottomley
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=20040117202107.GA8301@praka.local.home \
--to=praka@users.sourceforge.net \
--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