Qlogic FC scsi_target ISP2310

[Fuujin Networks LLC]

Alex:

Thanks very much for your input and assistance! I'm by no means an 
expert with FC on FreeBSD, but since it's my OS of choice I'm trying to 
fight through this one.

The fresh install is using your patch, so I believe everything is 
working correctly there. :)

I've noticed a few things about the isp driver that make me a bit 
nervous though. When I booted after a fresh install, I found that the 
system (initiator) hangs if the target is up and on the loop. Then the 
system comes up after I physically unplug the link. Plugging it back in 
doesn't produce any error messages on either end, but the target won't 
panic, and the initiator spits out the error I included in the previous 
email.

I'm starting the scsi target with "./scsi_target -d 0:2:0 backing.file" 
and rescanning the initiator with "camcontrol rescan all". This 
generally caused a core dump/kernel panic, but doesn't seem to be doing 
this now (for no reason evident to me anyway)...

Is there something particular about these cards and the SCSI bus:id:lun 
that I'm missing? Perhaps in the cards configuration settings? It 
appears from the man page for ISP that the driver ignores settings on 
the card. Is this actually the case??

BTW: I appreciate your assistance during a holiday weekend of all 
things! Proves once again why open source is the way to go!!

Erich M. Jenkins
Fuujin Networks, LLC
PO Box 792
Brainerd, MN 56401
(p) 218-824-5038
(f) 218-824-7516

"You should never, never doubt what no one is sure about."
-- Gene Wilder

Alexander Sack wrote:
> On Sun, Aug 31, 2008 at 8:00 AM, Fuujin Networks LLC
> <erich at fuujinnetworks.com> wrote:
>> I apologize for not being more specific in my questions. I understand that
>> we're loading the firmware via the kernel, but my question was why not load
>> it from the card? If I have an HP SmartArray 5300 card and the firmware is
>> out of date, I'm expected to update it, not load a kernel module to do it
>> for me. This makes sense for many reasons, not he least of which is
>> compatibility. I'm in no position to suggest what is proper from the
>> standpoint of this particular problem, but I'm trying to understand the
>> reason for choosing a kernel module rather than an sys admin as with nearly
>> all other devices.
> 
> We do both!  QLogic ships each card with some version of the firmware
> on it that boots up at runtime.  One of the nice features of the ISP
> is that its RISC based firmware can be updated at runtime ensuring you
> are always running the latest.  The ispfw driver is strictly used to
> register firmwares with the generic firmware driver (the real action
> happens in isp during isp_reset()).
> 
> I think the driver should really check to see if the ispfw version is
> less than the resident driver and do the right thing.  I think it used
> to do that but was taken out, I don't know why - I'm actually thinking
> of maybe it should be added back.
> 
> In any event, if you want to disable loading of the firmware you can
> set in your hints file:
> 
> hint.isp.0.fwload_disable=1
> 
> That should prevent the driver from loading the ispfw version (please
> check during bootup what version your resident firmware is at to
> determine which is newer).  If you do this then you should see:
> 
> isp0: Board Type 2300, Chip Revision 0x1, resident F/W Revision <version string>
> 
> instead of
> 
> isp0: Board Type 2300, Chip Revision 0x1, loaded F/W Revision <version string>
> 
> Having a separate utility (typically DOS or Windows based) is not that
> great in my eyes but to each his own.  Bottom line is you should run
> the latest ISP firmware (whether its the one that was flashed from
> QLogic or the one in the ispfw driver).  I'm thinking that perhaps and
> audit should be done and we should ship the latest firmware off the
> QLogic website.  What version is shipped with your card?  Looks like
> 3.3.25 is the latest for 23xx cards.  Hmmm....
> 
>> I misunderstood the purpose of your patch as well. I thought the problem
>>  was a firmware loading issue, but as you mentioned, this does not appear to
>> be the case.
> 
> Right, it seems something else.
> 
>> I did see your message with the patch and it was correctly applied and the
>> kernel was correctly compiled. I did, however, reinstall the OS because of
>> all the fiddling I did to this point. Funny thing is that I can't get it to
>> crash anymore. I tried it clean, and the system tanked, but after I applied
>> your patch, I can't get it to panic anymore. The loop looks like it comes
>> up, but when I rescan with the initiator, the target stays up without
>> incident, but nothing shows up in camcontrol as an emulated disk:
>>
>> amd_svr0-01# camcontrol devlist -v
>> 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)
>>
>> I do get this on the initiator though:
>>
>> [snip]
>> Aug 31 05:44:34 test kernel: isp0: bad underrun for 0.5 (count 36, resid 36,
>> status not marked)
>> Aug 31 05:44:34 test kernel: isp0: bad underrun for 0.6 (count 36, resid 36,
>> status not marked)
>> Aug 31 05:44:34 test kernel: isp0: bad underrun for 0.5 (count 36, resid 36,
>> status not marked)
>> Aug 31 05:44:34 test kernel: isp0: bad underrun for 0.6 (count 36, resid 36,
>> status not marked)
>> Aug 31 05:44:34 test kernel: isp0: bad underrun for 0.5 (count 36, resid 36,
>> status not marked)
>> Aug 31 05:44:34 test kernel: isp0: bad underrun for 0.6 (count 36, resid 36,
>> status not marked)
>> Aug 31 05:44:34 test kernel: isp0: bad underrun for 0.5 (count 36, resid 36,
>> status not marked)
>> Aug 31 05:44:34 test kernel: isp0: bad underrun for 0.6 (count 36, resid 36,
>> status not marked)
>> Aug 31 05:44:34 test kernel: isp0: bad underrun for 0.6 (count 36, resid 36,
>> status not marked)
>> Aug 31 05:44:34 test kernel: isp0: bad underrun for 0.7 (count 36, resid 36,
>> status not marked)
>> [snip]
>>
>> After a clean install, this is what I see from dmesg on the target:
>>
>> [snip]
>> registered firmware set <isp_1040>
>> registered firmware set <isp_1040_it>
>> registered firmware set <isp_1080>
>> registered firmware set <isp_1080_it>
>> registered firmware set <isp_12160>
>> registered firmware set <isp_12160_it>
>> registered firmware set <isp_2100>
>> registered firmware set <isp_2200>
>> registered firmware set <isp_2300>
>> registered firmware set <isp_2322>
>> registered firmware set <isp_2400>
>> isp0: <Qlogic ISP 2300 PCI FC-AL Adapter> port 0x3000-0x30ff mem
>> 0xfe020000-0xfe020fff irq 25 at device 1.0 on pci2
>> isp0: [ITHREAD]
>> isp0: Board Type 2300, Chip Revision 0x1, loaded F/W Revision 3.3.19
>> isp0: target notify code 0x1007
>> isp0: target notify code 0x1007
>> isp0: target notify code 0x1007
>> isp0: target notify code 0x1008
>> isp0: target notify code 0x1006
>> [snip]
> 
> Is this with or without the isp patch I sent regarding the firmware?
> I noticed its not trying to get isp_2300_it like before (I'm hoping
> that's due to the patch I sent otherwise I'm confused this holiday
> weekend).
> 
>> Here's the complete kernel, also after a fresh install and the removal of
>> unnecessary options/devices (stuff not in the server):
> 
>> # SCSI Controllers
>> device          isp             # Qlogic family
>> device          ispfw           # Firmware for QLogic HBAs- normally a
>> module
>> options         ISP_TARGET_MODE # for ISP cards to operate in target mode
>> device          targ            # SCSI Target device
>> device          targbh          # SCSI Target Black Hole
>> options         CAMDEBUG
>> options         VFS_AIO
> 
> Thanks for this, I just wanted to verify your build options look good.
> 
>> Not sure what to make of this.... Would you recommend a different FC card?
>> Emulex?
> 
> I have no direct experience with Emulex with FreeBSD so I'm not the
> right person to ask.  I was under the impression that the 23xx target
> mode was working.  Did you enable target mode in the BIOS by chance
> (or disable it, I think on my 24xx BIOS I have that option but I'm not
> in front of it yet).  Just verify your BIOS version number and options
> before completely giving up!  :D
> 
> -aps