From: Tony Battersby <tonyb@cybernetics.com>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>,
Nilesh Javali <njavali@marvell.com>,
GR-QLogic-Storage-Upstream@marvell.com,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
target-devel@vger.kernel.org, scst-devel@lists.sourceforge.net,
KERNEL ML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 14/15] scsi: qla2xxx: add back SRR support
Date: Thu, 25 Sep 2025 15:30:56 -0400 [thread overview]
Message-ID: <9ef32bd2-1370-4e57-a696-7151c8e46976@cybernetics.com> (raw)
In-Reply-To: <ec5bed6f-195f-486c-8905-bf63c663c212@cybernetics.com>
On 9/25/25 13:00, Tony Battersby wrote:
> On 9/25/25 12:04, Tony Battersby wrote:
>> On 9/25/25 11:30, Xose Vazquez Perez wrote:
>>> On 9/25/25 2:49 PM, Xose Vazquez Perez wrote:
>>>
>>>> If you want to review the firmware changelog, mainly: FCD-1183 (FCD-371, ER147301), FCD-259, ER146998
>>>> (from 9.00.00 to 9.15.05 [06/10/25]):
>>>> https://www.marvell.com/content/dam/marvell/en/drivers/2025-06-10-release/fw_release_notes/Fibre_Channel_Firmware_Release_Notes.pdf
>>>>
>>>> It's look like all 2{678}xx devices/chips are affected by this bug.
>>>> Perhaps the Marvel crew could provide more information on this.
>>> 267x, or older, is still on 8.08, so apparently it's free of this bug:
>>> https://www.marvell.com/content/dam/marvell/en/drivers/release-matrix/release-matrix-qlogic-fc-sw-posting-by-release-matrix.pdf
>>>
>>> 2870 / 2770 : 9.15.06 FW
>>> 2740 / 2760 / 269x : 9.15.01 FW
>>> 267x : 8.08.231 FW
>> I am still trying to figure out what macros to use to test for the
>> affected HBAs. So far I have:
>>
>> if (IS_QLA27XX(ha) || IS_QLA28XX(ha))
>>
>> But all the ISP numbers are pretty confusing. I have a number of 8, 16,
>> 32, and 64 Gbps HBAs lying around to test, but I am sure I don't have
>> every possible model.
>>
>> There are a number of items under "Changes and Fixes from v9.08.00 to
>> v9.09.00" that might be related to the problem that I was experiencing.
>> For example FCD-1076 sounds similar except that the SRR problem was with
>> the CTIO queue rather than the ATIO queue. I could expand the "bad
>> firmware" versions to include v9.04.00 - v9.08.00, since v9.04.00
>> introduced ER147301 and v9.09.00 fixed FCD-1183.
>>
>> Thanks,
>> Tony
>>
> This is what I found by checking the PCI IDs on some of my HBAs:
>
> not affected
> QLE2672 16 Gbps ISP2031 8.08.231 FW
>
> affected
> QLE2694 16 Gpbs ISP2071 (tested)
> QLE2742 32 Gbps ISP2261 (not tested)
> QLE2872 64 Gpbs ISP2281 (not tested)
>
> So the following check should cover them:
>
> if (IS_QLA27XX(ha) || IS_QLA28XX(ha))
>
> Tony
>
Here is the updated version of the function:
/*
* Return true if the HBA firmware version is known to have bugs that
* prevent Sequence Level Error Recovery (SLER) / Sequence Retransmission
* Request (SRR) from working.
*
* Some bad versions are based on testing and some are based on "Marvell Fibre
* Channel Firmware Release Notes".
*/
static bool qlt_has_sler_fw_bug(struct qla_hw_data *ha)
{
bool has_sler_fw_bug = false;
if (IS_QLA27XX(ha) || IS_QLA28XX(ha)) {
/*
* In the fw release notes:
* ER147301 was added to v9.05.00 causing SLER regressions
* FCD-259 was fixed in v9.08.00
* FCD-371 was fixed in v9.08.00
* FCD-1183 was fixed in v9.09.00
*
* QLE2694L (ISP2071) known bad firmware (tested):
* 9.06.02
* 9.07.00
* 9.08.02
* SRRs trigger hundreds of bogus entries in the response
* queue and various other problems.
*
* QLE2694L known good firmware (tested):
* 8.08.05
* 9.09.00
*
* Suspected bad firmware (not confirmed by testing):
* v9.05.xx
*
* unknown firmware:
* 9.00.00 - 9.04.xx
*/
if (ha->fw_major_version == 9 &&
ha->fw_minor_version >= 5 &&
ha->fw_minor_version <= 8)
has_sler_fw_bug = true;
}
return has_sler_fw_bug;
}
next prev parent reply other threads:[~2025-09-25 19:49 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-08 18:45 [PATCH 00/15] qla2xxx target mode improvements Tony Battersby
2025-09-08 18:47 ` [PATCH 01/15] Revert "scsi: qla2xxx: Perform lockless command completion in abort path" Tony Battersby
2025-09-08 18:48 ` [PATCH 02/15] scsi: qla2xxx: fix initiator mode with qlini_mode=exclusive Tony Battersby
2025-09-08 18:50 ` [PATCH 03/15] scsi: qla2xxx: fix lost interrupts with qlini_mode=disabled Tony Battersby
2025-09-08 18:51 ` [PATCH 04/15] scsi: qla2xxx: use reinit_completion on mbx_intr_comp Tony Battersby
2025-09-08 18:53 ` [PATCH 05/15] scsi: qla2xxx: remove code for unsupported hardware Tony Battersby
2025-09-08 18:54 ` [PATCH 06/15] scsi: qla2xxx: improve debug output for term exchange Tony Battersby
2025-09-08 18:56 ` [PATCH 07/15] scsi: qla2xxx: fix term exchange when cmd_sent_to_fw == 1 Tony Battersby
2025-09-08 18:58 ` [PATCH 08/15] scsi: qla2xxx: fix oops during cmd abort Tony Battersby
2025-09-08 18:59 ` [SCST PATCH " Tony Battersby
2025-09-11 14:21 ` [PATCH " Dmitry Bogdanov
2025-09-24 19:41 ` Tony Battersby
2025-09-24 19:43 ` [PATCH v2 09/16] scsi: qla2xxx: fix races with aborting commands Tony Battersby
2025-09-24 19:45 ` [SCST PATCH " Tony Battersby
2025-09-25 8:42 ` [DMARC Error]Re: [PATCH 08/15] scsi: qla2xxx: fix oops during cmd abort Dmitry Bogdanov
2025-09-08 19:01 ` [PATCH 09/15] scsi: qla2xxx: improve checks in qlt_xmit_response / qlt_rdy_to_xfer Tony Battersby
2025-09-08 19:02 ` [PATCH 10/15] scsi: qla2xxx: fix TMR failure handling Tony Battersby
2025-09-12 14:36 ` Dmitry Bogdanov
2025-09-16 16:04 ` Tony Battersby
2025-09-17 13:06 ` [DMARC Error]Re: " Dmitry Bogdanov
2025-09-17 20:38 ` Tony Battersby
2025-09-08 19:04 ` [PATCH 11/15] scsi: qla2xxx: fix invalid memory access with big CDBs Tony Battersby
2025-09-08 19:05 ` [SCST PATCH " Tony Battersby
2025-09-08 19:07 ` [PATCH 12/15] scsi: qla2xxx: add cmd->rsp_sent Tony Battersby
2025-09-08 19:08 ` [SCST PATCH " Tony Battersby
2025-09-15 13:47 ` [PATCH " Dmitry Bogdanov
2025-09-24 20:04 ` Tony Battersby
2025-09-08 19:09 ` [PATCH 13/15] scsi: qla2xxx: improve cmd logging Tony Battersby
2025-09-08 19:10 ` [PATCH 14/15] scsi: qla2xxx: add back SRR support Tony Battersby
2025-09-08 19:11 ` [SCST PATCH " Tony Battersby
2025-09-25 12:49 ` [PATCH " Xose Vazquez Perez
2025-09-25 15:30 ` Xose Vazquez Perez
2025-09-25 16:04 ` Tony Battersby
2025-09-25 17:00 ` Tony Battersby
2025-09-25 19:30 ` Tony Battersby [this message]
2025-09-08 19:13 ` [PATCH 15/15] scsi: qla2xxx: improve safety of cmd lookup by handle Tony Battersby
2025-09-08 19:14 ` [SCST PATCH] qla2x00t-32gbit: add on_abort_cmd callback Tony Battersby
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9ef32bd2-1370-4e57-a696-7151c8e46976@cybernetics.com \
--to=tonyb@cybernetics.com \
--cc=GR-QLogic-Storage-Upstream@marvell.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=njavali@marvell.com \
--cc=scst-devel@lists.sourceforge.net \
--cc=target-devel@vger.kernel.org \
--cc=xose.vazquez@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®