Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 1 Aug 2023 21:10:26 -0400
From:      Brian McGovern <rogan.mcgovern@gmail.com>
To:        Joerg Pulz <Joerg.Pulz@frm2.tum.de>
Cc:        questions@freebsd.org
Subject:   Re: isp support for QLogic 2722/firmware?
Message-ID:  <CAPe4eRRauptqZgYfirSyQ4GWDr4fYZQ%2B9Rw4b4GVmPLOf1iwew@mail.gmail.com>
In-Reply-To: <6on92p68-rpq2-594p-8q5s-979ns8p12653@sez2.ghz.qr>
References:  <CAPe4eRRB9o6CfijMfdxDMQFDKuxe9-C4D=FLkVpmDMn5kZz00w@mail.gmail.com> <5cf2f487-a5d2-55b7-49df-51690ac22412@aetern.org> <CAPe4eRRKhgALVumtNfVQ2bhEm8y9HX3U02=UNB2udjMvuV40Sg@mail.gmail.com> <6on92p68-rpq2-594p-8q5s-979ns8p12653@sez2.ghz.qr>

next in thread | previous in thread | raw e-mail | index | archive | help
--000000000000abde550601e654d4
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Joerg,
  Sorry it took me a few days to get back to you and the list. Thank you
for answering the questions I asked. It required a firmware upgrade that
had previously caused problems with VMWare's ESXi.

  The fact that someone was using the adapters, despite not a lot mentioned
over the last few years during my Google search, meant I wasn't wasting my
time chasing a problem that had no solution. Mentioning the card should be
using the onboard firmware pointed me in the right direction.

  Everything appears to be working now. The only open issue I have is
making sure that the multi-path is working when I get the machine moved to
the production network.

     -Brian

On Thu, Jul 27, 2023 at 5:40=E2=80=AFAM Joerg Pulz <Joerg.Pulz@frm2.tum.de>=
 wrote:

> On Wed, 26 Jul 2023, Brian McGovern wrote:
>
> > >> I'm curious if anyone has this working, and if so, any chance I can
> >>> obtain the firmware or process you are using? I'm hoping its somethin=
g
> >>> like flashing an image to the card with some other OS first. TIA
> >
> >> Support for this (and some other newer HBAs) was added recently to
> >> 14-CURRENT, see latest commits in
> >> https://cgit.freebsd.org/src/log/sys/dev/isp
> > <https://cgit.freebsd.org/src/log/sys/dev/isp>.
> >
> > Its getting late locally, so take this with a grain of salt... I'm pret=
ty
> > sure I grabbed the main branch from git, and effectively did a MFC
> (working
> > with 13.2-RELEASE). Looking at the diffs you pointed me to vs. whats on
> the
> > disk, it looks like I have the latest bits, but I'll check it again
> > tomorrow to be sure. Its possible I'm missing something.
> >
> > The problem is consistent. When the adapters try to come up, and I'm
> using
> > them as kernel modules right now just so I can cycle through testing
> > faster, I continue to get
> >
> > "isp_2700 could not load firmware image, error 2"
> >
> > if I don't hack up the ispfw driver/module to have something that meets
> the
> > name requirements for "isp_2700" firmware.
> >
> > and if I try to create a firmware module it can install with the
> > bk014519.bin firmware file, it'll happily find something for firmware,
> but
> > then throws a:
> > isp0: Mailbox Command (0xb) Timeout (100000us) (isp_reset:373)
> > isp0: Mailbox Command 'LOAD RISC RAM' failed (TIMEOUT)
> > isp0: F/W download failed
> > isp0: isp_reinit: cannot reset card
> > device_attach: isp0 attach returned 6
> >
> > So, what I think is missing is either a.) finding a good firmware image
> > that I can load via the driver, or b.) figuring out how to flash firmwa=
re
> > to the adapter via some other means, and figure out how to skip the loa=
d
> > step when the driver starts. Hence why I'm hoping to find someone who h=
as
> > the card working, so I can clone their process.
> >
> > But, if anyone has other ideas, I'm all ears.
> >
> >     -Brian
> >
> > On Wed, Jul 26, 2023 at 8:55?PM Yuri <yuri@aetern.org> wrote:
> >
> >> Brian McGovern wrote:
> >>> Quick question about the isp and card support. I have an HPE branded
> >>> Qlogic ISP 2722 that I'm trying to bring online. Following the variou=
s
> >>> tutorials I loaded ispfw, then the isp driver. I got an error message
> >>> "isp_2700 could not load firmware image, error 2". The boards don't
> come
> >>> online.
> >>>
> >>> Looking at the man page, it appears supported on the Qlogic
> >>> 2740/2742/2764 (aka 2722/2714) line, so I tried to chase down some
> >>> firmware and duplicate the isp_2400 and isp_2500 functionality with t=
he
> >>> .bin file. Now, it tries to load but I get a firmware loading failure=
.
> >>> I'm assuming that either current versions and .bin files are
> >>> incompatible with the other loading processes, or I just screwed
> >>> something up in all the translation (I found a bk014519.bin file).
> >>>
> >>> I'm curious if anyone has this working, and if so, any chance I can
> >>> obtain the firmware or process you are using? I'm hoping its somethin=
g
> >>> like flashing an image to the card with some other OS first. TIA
> >>
> >> Support for this (and some other newer HBAs) was added recently to
> >> 14-CURRENT, see latest commits in
> >> https://cgit.freebsd.org/src/log/sys/dev/isp.
>
> Those HBAs are supported since 2018-02-28.
> So support for them is in 13.2 - I have systems running with those:
>
> # uname -r
> 13.2-RELEASE
>
> # dmesg -a |grep isp
> isp0: <Qlogic ISP 2722 PCI FC Adapter> mem
> 0x93302000-0x93302fff,0x93300000-0x93301fff,0x93200000-0x932fffff at devi=
ce
> 0.0 on pci1
>
> # sysctl dev.isp.0
> dev.isp.0.%pnpinfo: vendor=3D0x1077 device=3D0x2261 subvendor=3D0x1077
> subdevice=3D0x029b class=3D0x0c0400
> dev.isp.0.%driver: isp
> dev.isp.0.%desc: Qlogic ISP 2722 PCI FC Adapter
>
> Recent changes in CURRENT are for the next gen HABs (28XX) and FLT/NVRAM
> handling, so no need to backport anything.
>
> There is no firmware for those HBAs included in ispfw(4) and there is no
> need for it.
> You should not try to simply add firmware to ispfw(4) without knowing how
> the driver has to load it into the HBA.
>
> The isp(4) driver checks for firmware availability by itself. For your
> HBA the firmware is loaded by isp(4) from the HBAs flash.
> If this is not working than the firmware on your HBAs flash may be broken
> and should be reflashed.
>
> Without further information it is hard to guess what's happening.
> You should:
> - revert everything to a clean 13.2-RELEASE
> - provide verbose pciconf(8) output for your HBA
> - set isp(4) debug level using kenv(8)
>    # kenv hint.isp.0.debug=3D0x3f
> - load isp(4)
>    # kldload isp
> - provide dmesg(8) output for isp(4) load/attach
>
> Joerg
>
> --
> The beginning is the most important part of the work.
>                                 -Plato

--000000000000abde550601e654d4
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Joerg,</div><div>=C2=A0 Sorry it took me a few days t=
o get back to you and the list. Thank you for answering the questions I ask=
ed. It required a firmware upgrade that had previously caused problems with=
 VMWare&#39;s ESXi.</div><div><br></div><div>=C2=A0 The fact that someone w=
as using the adapters, despite not a lot mentioned over the last few years =
during my Google search, meant I wasn&#39;t wasting my time chasing a probl=
em that had no solution. Mentioning the card should be using the onboard fi=
rmware pointed me in the right direction. <br></div><div><br></div><div>=C2=
=A0 Everything appears to be working now. The only open issue I have is mak=
ing sure that the multi-path is working when I get the machine moved to the=
 production network.</div><div><br></div><div>=C2=A0=C2=A0=C2=A0=C2=A0 -Bri=
an<br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"=
gmail_attr">On Thu, Jul 27, 2023 at 5:40=E2=80=AFAM Joerg Pulz &lt;<a href=
=3D"mailto:Joerg.Pulz@frm2.tum.de">Joerg.Pulz@frm2.tum.de</a>&gt; wrote:<br=
></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;=
border-left:1px solid rgb(204,204,204);padding-left:1ex">On Wed, 26 Jul 202=
3, Brian McGovern wrote:<br>
<br>
&gt; &gt;&gt; I&#39;m curious if anyone has this working, and if so, any ch=
ance I can<br>
&gt;&gt;&gt; obtain the firmware or process you are using? I&#39;m hoping i=
ts something<br>
&gt;&gt;&gt; like flashing an image to the card with some other OS first. T=
IA<br>
&gt;<br>
&gt;&gt; Support for this (and some other newer HBAs) was added recently to=
<br>
&gt;&gt; 14-CURRENT, see latest commits in<br>
&gt;&gt; <a href=3D"https://cgit.freebsd.org/src/log/sys/dev/isp" rel=3D"no=
referrer" target=3D"_blank">https://cgit.freebsd.org/src/log/sys/dev/isp</a=
><br>
&gt; &lt;<a href=3D"https://cgit.freebsd.org/src/log/sys/dev/isp" rel=3D"no=
referrer" target=3D"_blank">https://cgit.freebsd.org/src/log/sys/dev/isp</a=
>&gt;.<br>
&gt;<br>
&gt; Its getting late locally, so take this with a grain of salt... I&#39;m=
 pretty<br>
&gt; sure I grabbed the main branch from git, and effectively did a MFC (wo=
rking<br>
&gt; with 13.2-RELEASE). Looking at the diffs you pointed me to vs. whats o=
n the<br>
&gt; disk, it looks like I have the latest bits, but I&#39;ll check it agai=
n<br>
&gt; tomorrow to be sure. Its possible I&#39;m missing something.<br>
&gt;<br>
&gt; The problem is consistent. When the adapters try to come up, and I&#39=
;m using<br>
&gt; them as kernel modules right now just so I can cycle through testing<b=
r>
&gt; faster, I continue to get<br>
&gt;<br>
&gt; &quot;isp_2700 could not load firmware image, error 2&quot;<br>
&gt;<br>
&gt; if I don&#39;t hack up the ispfw driver/module to have something that =
meets the<br>
&gt; name requirements for &quot;isp_2700&quot; firmware.<br>
&gt;<br>
&gt; and if I try to create a firmware module it can install with the<br>
&gt; bk014519.bin firmware file, it&#39;ll happily find something for firmw=
are, but<br>
&gt; then throws a:<br>
&gt; isp0: Mailbox Command (0xb) Timeout (100000us) (isp_reset:373)<br>
&gt; isp0: Mailbox Command &#39;LOAD RISC RAM&#39; failed (TIMEOUT)<br>
&gt; isp0: F/W download failed<br>
&gt; isp0: isp_reinit: cannot reset card<br>
&gt; device_attach: isp0 attach returned 6<br>
&gt;<br>
&gt; So, what I think is missing is either a.) finding a good firmware imag=
e<br>
&gt; that I can load via the driver, or b.) figuring out how to flash firmw=
are<br>
&gt; to the adapter via some other means, and figure out how to skip the lo=
ad<br>
&gt; step when the driver starts. Hence why I&#39;m hoping to find someone =
who has<br>
&gt; the card working, so I can clone their process.<br>
&gt;<br>
&gt; But, if anyone has other ideas, I&#39;m all ears.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0-Brian<br>
&gt;<br>
&gt; On Wed, Jul 26, 2023 at 8:55?PM Yuri &lt;<a href=3D"mailto:yuri@aetern=
.org" target=3D"_blank">yuri@aetern.org</a>&gt; wrote:<br>
&gt;<br>
&gt;&gt; Brian McGovern wrote:<br>
&gt;&gt;&gt; Quick question about the isp and card support. I have an HPE b=
randed<br>
&gt;&gt;&gt; Qlogic ISP 2722 that I&#39;m trying to bring online. Following=
 the various<br>
&gt;&gt;&gt; tutorials I loaded ispfw, then the isp driver. I got an error =
message<br>
&gt;&gt;&gt; &quot;isp_2700 could not load firmware image, error 2&quot;. T=
he boards don&#39;t come<br>
&gt;&gt;&gt; online.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Looking at the man page, it appears supported on the Qlogic<br=
>
&gt;&gt;&gt; 2740/2742/2764 (aka 2722/2714) line, so I tried to chase down =
some<br>
&gt;&gt;&gt; firmware and duplicate the isp_2400 and isp_2500 functionality=
 with the<br>
&gt;&gt;&gt; .bin file. Now, it tries to load but I get a firmware loading =
failure.<br>
&gt;&gt;&gt; I&#39;m assuming that either current versions and .bin files a=
re<br>
&gt;&gt;&gt; incompatible with the other loading processes, or I just screw=
ed<br>
&gt;&gt;&gt; something up in all the translation (I found a bk014519.bin fi=
le).<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; I&#39;m curious if anyone has this working, and if so, any cha=
nce I can<br>
&gt;&gt;&gt; obtain the firmware or process you are using? I&#39;m hoping i=
ts something<br>
&gt;&gt;&gt; like flashing an image to the card with some other OS first. T=
IA<br>
&gt;&gt;<br>
&gt;&gt; Support for this (and some other newer HBAs) was added recently to=
<br>
&gt;&gt; 14-CURRENT, see latest commits in<br>
&gt;&gt; <a href=3D"https://cgit.freebsd.org/src/log/sys/dev/isp" rel=3D"no=
referrer" target=3D"_blank">https://cgit.freebsd.org/src/log/sys/dev/isp</a=
>.<br>
<br>
Those HBAs are supported since 2018-02-28.<br>
So support for them is in 13.2 - I have systems running with those:<br>
<br>
# uname -r<br>
13.2-RELEASE<br>
<br>
# dmesg -a |grep isp<br>
isp0: &lt;Qlogic ISP 2722 PCI FC Adapter&gt; mem 0x93302000-0x93302fff,0x93=
300000-0x93301fff,0x93200000-0x932fffff at device 0.0 on pci1<br>
<br>
# sysctl dev.isp.0<br>
dev.isp.0.%pnpinfo: vendor=3D0x1077 device=3D0x2261 subvendor=3D0x1077 subd=
evice=3D0x029b class=3D0x0c0400<br>
dev.isp.0.%driver: isp<br>
dev.isp.0.%desc: Qlogic ISP 2722 PCI FC Adapter<br>
<br>
Recent changes in CURRENT are for the next gen HABs (28XX) and FLT/NVRAM <b=
r>
handling, so no need to backport anything.<br>
<br>
There is no firmware for those HBAs included in ispfw(4) and there is no <b=
r>
need for it.<br>
You should not try to simply add firmware to ispfw(4) without knowing how <=
br>
the driver has to load it into the HBA.<br>
<br>
The isp(4) driver checks for firmware availability by itself. For your <br>
HBA the firmware is loaded by isp(4) from the HBAs flash.<br>
If this is not working than the firmware on your HBAs flash may be broken <=
br>
and should be reflashed.<br>
<br>
Without further information it is hard to guess what&#39;s happening.<br>
You should:<br>
- revert everything to a clean 13.2-RELEASE<br>
- provide verbose pciconf(8) output for your HBA<br>
- set isp(4) debug level using kenv(8)<br>
=C2=A0 =C2=A0# kenv hint.isp.0.debug=3D0x3f<br>
- load isp(4)<br>
=C2=A0 =C2=A0# kldload isp<br>
- provide dmesg(8) output for isp(4) load/attach<br>
<br>
Joerg<br>
<br>
-- <br>
The beginning is the most important part of the work.<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 -Plato</blockquote></div>

--000000000000abde550601e654d4--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPe4eRRauptqZgYfirSyQ4GWDr4fYZQ%2B9Rw4b4GVmPLOf1iwew>