QLogic 2360 FC HBAs not playing well with others

[Brad Waite]

Alexander Sack wrote:
> On Fri, Apr 9, 2010 at 2:29 PM, Brad Waite <freebsd at wcubed.net> wrote:
>> I beseech you, oh great masters of SCSI and fibre channel, hear my pleas
>> for help!
>>
>> My 2 QLE2360s don't appear to be waking up properly in a Dell R710
>> running 7.2 AMD64.  At the very least, they're not recognizing any of
>> the volumes on the Sun 2540 array in the fabric.  Everything works just
>> fine under VMware ESXi 4.1, though.
>>
>> Here's the relevant dmesg output:
>>
>> 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 2322 PCI FC-AL Adapter> port 0xec00-0xecff mem
>> 0xdf2ff000-0xdf2fffff irq 47 at device 7.0 on pci7
>> isp0: setting role to 0x2
>> isp0: [ITHREAD]
>> isp0: Board Type 2322, Chip Revision 0x3, loaded F/W Revision 3.3.19
>> ...
>> isp1: <Qlogic ISP 2322 PCI FC-AL Adapter> port 0xdc00-0xdcff mem
>> 0xdf3ff000-0xdf3fffff irq 49 at device 7.0 on pci11
>> isp1: setting role to 0x2
>> isp1: [ITHREAD]
>> isp1: Board Type 2322, Chip Revision 0x3, loaded F/W Revision 3.3.19
>> ...
>> isp0: Interrupting Mailbox Command (0x69) Timeout (100000us)
>> isp0: Mailbox Command 'GET FW STATE' failed (TIMEOUT)
>> isp1: Interrupting Mailbox Command (0x69) Timeout (100000us)
>> isp1: Mailbox Command 'GET FW STATE' failed (TIMEOUT)
>> [lather, rinse, repeat]
>>
>> Other than the flash drive (da0), no other da disks appear.
>>
>> I've tried adding the following to /boot/device.hints and
>> /boot/loader.conf respectively with no change in results:
>>
>> hint.isp.0.fullduplex="1"
>> hint.isp.0.topology="nport"
>> hint.isp.0.role="2"
>> hint.isp.1.fullduplex="1"
>> hint.isp.1.topology="nport"
>> hint.isp.1.role="2"
>>
>> ispfw_load="YES"
>>
>> What could be wrong?
> 
> Well the GET FW STATE seems like the ISP didn't boot up properly for
> whatever reason.  Do you know what firmware is shipped on the card?
> i.e. if you do ispfw_load="NO" which means we are going to boot up the
> shipped firmware (which maybe newer, I believe 3.3.25 is the latest
> but don't hold me to the fire on that).  I don't think those hints are
> necessary (or at least shouldn't be).
> 
> -aps

Here's what I get w/ispfw_load="NO":

isp0: <Qlogic ISP 2322 PCI FC-AL Adapter> port 0xec00-0xecff mem 0xdf2ff000-0xdf2fffff irq 47 at device 7.0 on pci7
isp0: setting role to 0x2
firmware_get: failed to load firmware image isp_2322
isp0: [ITHREAD]
isp0: Board Type 2322, Chip Revision 0x3, resident F/W Revision 3.3.7
...
isp1: <Qlogic ISP 2322 PCI FC-AL Adapter> port 0xdc00-0xdcff mem 0xdf3ff000-0xdf3fffff irq 49 at device 7.0 on pci11
isp1: setting role to 0x2
firmware_get: failed to load firmware image isp_2322
isp1: [ITHREAD]
isp1: Board Type 2322, Chip Revision 0x3, resident F/W Revision 3.3.7
...
isp0: Interrupting Mailbox Command (0x69) Timeout (100000us)
isp0: Mailbox Command 'GET FW STATE' failed (TIMEOUT)
isp1: Interrupting Mailbox Command (0x69) Timeout (100000us)
isp1: Mailbox Command 'GET FW STATE' failed (TIMEOUT)

According to the system's BIOS, they're sharing IRQ10.  Changing the IRQ on one automatically changes it on the other
(and one of the USB controllers).  I assume that's due to the slots and/bus.

Other than that, I'm scratching my head.

Any help is appreciated.