Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

freebsd-scsi Digest, Vol 363, Issue 5

8 views
Skip to first unread message

freebsd-sc...@freebsd.org

unread,
Apr 10, 2010, 8:00:26 AM4/10/10
to freebs...@freebsd.org
Send freebsd-scsi mailing list submissions to
freebs...@freebsd.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-scsi
or, via email, send a message with subject or body 'help' to
freebsd-sc...@freebsd.org

You can reach the person managing the list at
freebsd-s...@freebsd.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-scsi digest..."


Today's Topics:

1. QLogic 2360 FC HBAs not playing well with others (Brad Waite)
2. Re: QLogic 2360 FC HBAs not playing well with others
(Alexander Sack)
3. Re: QLogic 2360 FC HBAs not playing well with others
(Matthew Jacob)
4. RE: QLogic 2360 FC HBAs not playing well with others
(Hearn, Trevor)
5. Re: QLogic 2360 FC HBAs not playing well with others (Brad Waite)


----------------------------------------------------------------------

Message: 1
Date: Fri, 09 Apr 2010 12:29:30 -0600
From: Brad Waite <fre...@wcubed.net>
Subject: QLogic 2360 FC HBAs not playing well with others
To: freebs...@freebsd.org
Message-ID: <4BBF720A...@wcubed.net>
Content-Type: text/plain; charset=UTF-8

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?


------------------------------

Message: 2
Date: Fri, 9 Apr 2010 15:03:27 -0400
From: Alexander Sack <pisy...@gmail.com>
Subject: Re: QLogic 2360 FC HBAs not playing well with others
To: Brad Waite <fre...@wcubed.net>
Cc: freebs...@freebsd.org
Message-ID:
<t2g3c0b01821004091203if...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Apr 9, 2010 at 2:29 PM, Brad Waite <fre...@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


------------------------------

Message: 3
Date: Fri, 09 Apr 2010 12:30:06 -0700
From: Matthew Jacob <m...@feral.com>
Subject: Re: QLogic 2360 FC HBAs not playing well with others
To: freebs...@freebsd.org
Message-ID: <4BBF803E...@feral.com>
Content-Type: text/plain; charset=UTF-8; format=flowed

On 04/09/2010 11:29 AM, Brad Waite 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.
>

Get newer firmware either by upgrading with RELENG_7 or snagging
asm_2300.h from RELENG_7 and rebuilding.

You don't have to load all of ispfw

isp2300_LOAD=YES

should get you just that onemodule

the latest in the FreeBSD tree is 3.03.26

------------------------------

Message: 4
Date: Fri, 9 Apr 2010 14:38:56 -0500
From: "Hearn, Trevor" <trevor...@Vanderbilt.Edu>
Subject: RE: QLogic 2360 FC HBAs not playing well with others
To: "freebs...@freebsd.org" <freebs...@freebsd.org>
Message-ID:
<D1858E36CEE14F429C373...@ITS-HCWNEM04.ds.Vanderbilt.edu>

Content-Type: text/plain; charset="us-ascii"

I had the same exact problem. I just loaded 7.3, and the problem went away. 6.4, and 8.0 worked like a charm. 7.2 gave me the same response no matter what I did. 7.3 seems to have cured whatever it was that was outta whack. Sorry if the explanation wasn't as technical as it should be, but there ya go. :)

-Trevor
________________________________________
From: owner-fre...@freebsd.org [owner-fre...@freebsd.org] On Behalf Of Matthew Jacob [m...@feral.com]
Sent: Friday, April 09, 2010 2:30 PM
To: freebs...@freebsd.org
Subject: Re: QLogic 2360 FC HBAs not playing well with others

On 04/09/2010 11:29 AM, Brad Waite 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.
>

Get newer firmware either by upgrading with RELENG_7 or snagging
asm_2300.h from RELENG_7 and rebuilding.

You don't have to load all of ispfw

isp2300_LOAD=YES

should get you just that onemodule

the latest in the FreeBSD tree is 3.03.26

------------------------------

Message: 5
Date: Fri, 09 Apr 2010 15:30:27 -0600
From: Brad Waite <fre...@wcubed.net>
Subject: Re: QLogic 2360 FC HBAs not playing well with others
To: Alexander Sack <pisy...@gmail.com>
Cc: freebs...@freebsd.org
Message-ID: <4BBF9C7...@wcubed.net>
Content-Type: text/plain; charset=UTF-8

Alexander Sack wrote:
> On Fri, Apr 9, 2010 at 2:29 PM, Brad Waite <fre...@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.


------------------------------

End of freebsd-scsi Digest, Vol 363, Issue 5
********************************************

0 new messages