Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 24 Aug 2013 13:51:02 +0200
From:      Ivan Voras <ivoras@freebsd.org>
To:        Matthew Jacob <mj@feral.com>
Cc:        freebsd-scsi@freebsd.org
Subject:   Re: QLogic (isp) problem
Message-ID:  <CAF-QHFVKWajEQ9o9SkjTgRPQE0Knco2x=z-P8j=C3iqHPus1cg@mail.gmail.com>
In-Reply-To: <alpine.LRH.2.03.1308230831220.31694@feral.com>
References:  <kv7guk$u25$1@ger.gmane.org> <alpine.LRH.2.03.1308230831220.31694@feral.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On 23 August 2013 17:34, Matthew Jacob <mj@feral.com> wrote:
>
>
> Ivan, I need some more information
>
> 1. What FreeBSD version and what qlogic hardware and are you loading
> the appropriate ispfw module for that card?

FreeBSD 9.1-RELEASE, here's what dmesg writes:

isp0: <Qlogic ISP 2432 PCI FC-AL Adapter> port 0x5000-0x50ff mem
0xfdff0000-0xfdff3fff irq 19 at device 0.0 on pci19
isp0: set PCI latency to 64
isp0: Board Type 2422, Chip Revision 0x3, loaded F/W Revision 5.4.0
isp0: 4096 max I/O command limit set
isp0: Chan 0 0x5001438003bddccd/0x5001438003bddccc Role Initiator
isp0: Starting Initial Loop Down Timer @ 1
isp1: <Qlogic ISP 2432 PCI FC-AL Adapter> port 0x5400-0x54ff mem
0xfdfe0000-0xfdfe3fff irq 16 at device 0.1 on pci19
isp1: set PCI latency to 64
isp1: Board Type 2422, Chip Revision 0x3, loaded F/W Revision 5.4.0
isp1: 4096 max I/O command limit set
isp1: Chan 0 0x5001438003bddccf/0x5001438003bddcce Role Initiator
isp1: Starting Initial Loop Down Timer @ 1

As for the firmware, the only thing I'm doing is having this:

ispfw_load="YES"

in my loader.conf.

If you need more information, you need to tell me how to obtain it.

> 2. What is the connection topology? Clearly there's a switch involved.
> What switch vendor?

Brocade. The topology is redundant: there are 2 of everything: the SAN
storage has two controllers, each connected to its own Brocade switch,
and the host isp device has two ports which are connected to one each
of the switches.

> 3. You mentioned an HP MSA 2000. How many other initiators are there
> on the fabric? Just the one I see coming and going?

I'm not that well versed in terminology, but from my interpretation of
your question, here's what we have: there are 7 more identical servers
which are connected identically to the whole setup. Not all of them
are up all the time. The MSA storage allows us to "map" certain
volumes to certain ports, which we do (not all of the servers can
access all of the volumes).

> 4. You say "spontaneous reboots". Some detail about this would be good.

That's the problem - I don't have any.
The only thing I have is that "something weird" happens with the isp
device (as seen in the logs) and the machine reboots. See what happens
at the timepoint Aug 20 15:03:23 in the log file I've linked to in my
original message.

Foremost, I'd like to know if you suspect this is a hardware error.



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?CAF-QHFVKWajEQ9o9SkjTgRPQE0Knco2x=z-P8j=C3iqHPus1cg>