From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 204815] qla2xxx: firmware is not responding to mailbox commands
Date: Fri, 13 Sep 2019 16:03:11 +0000 [thread overview]
Message-ID: <bug-204815-11613-TklCnS3jym@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-204815-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=204815
--- Comment #3 from Roman Bolshakov (r.bolshakov@yadro.com) ---
Hi Martin,
I can't tell for sure, because f8f97b0c5b7f7 introduces a regression fixed in
1710ac17547ac8b ("scsi: qla2xxx: Fix read offset in
qla24xx_load_risc_flash()").
Here's the possible timeline:
1. f8f97b0c5b7f7 ("scsi: qla2xxx: Cleanups for NVRAM/Flash read/write path")
introduces a regression which prevents successful ISP firmware checksum
validation and kernel panics shortly after.
2. a28d9e4ef997 ("scsi: qla2xxx: Add support for multiple fwdump
templates/segments") introduces a regression which causes EEH and system lockup
on POWER8 or makes firmware unavailable (this bug).
3. 1710ac17547ac8 ("scsi: qla2xxx: Fix read offset in
qla24xx_load_risc_flash()") fixes f8f97b0c5b7f7 but the fix depends both on #1
and #2.
4. edbd56472a63 ("scsi: qla2xxx: qla2x00_alloc_fw_dump: set ha->eft") fixes
a28d9e4ef997.
It's not possible to bisect between #1 and #3 because of the panic introduced
in #1. And firmware works reliably only after #4.
And I think it's important to include your fix into 5.3, otherwise qla2xxx is
broken in the release.
Thanks,
Roman
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2019-09-13 16:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 15:54 [Bug 204815] New: qla2xxx: firmware is not responding to mailbox commands bugzilla-daemon
2019-09-11 15:55 ` [Bug 204815] " bugzilla-daemon
2019-09-11 15:57 ` bugzilla-daemon
2019-09-13 15:04 ` bugzilla-daemon
2019-09-13 16:03 ` bugzilla-daemon [this message]
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=bug-204815-11613-TklCnS3jym@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.