From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 204815] New: qla2xxx: firmware is not responding to mailbox commands
Date: Wed, 11 Sep 2019 15:54:28 +0000 [thread overview]
Message-ID: <bug-204815-11613@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=204815
Bug ID: 204815
Summary: qla2xxx: firmware is not responding to mailbox
commands
Product: SCSI Drivers
Version: 2.5
Kernel Version: 5.2-rc1 up to 5.3-rc8
Hardware: PPC-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: QLOGIC QLA2XXX
Assignee: scsi_drivers-qla2xxx@kernel-bugs.osdl.org
Reporter: r.bolshakov@yadro.com
Regression: No
Created attachment 284925
--> https://bugzilla.kernel.org/attachment.cgi?id=284925&action=edit
firmware times out on 5.3-rc8
I'm using QLogic HBAs (QLE2560 and QLE2742) inside pseries guests on
ppc64le/POWER8 hypervisor and they are not usable since commit f8f97b0c5b7f7
("scsi: qla2xxx: Cleanups for NVRAM/Flash read/write path").
The firmware stops responding to mailbox commands shortly after system boot is
done.
That also triggers an EEH on pseries machine and driver doesn't handle the EEH
properly because firmware is effectively not available. I disabled eeh inside
the guest as it caused a deadlock on the host kernel.
The issue is fixed in linux-next by the commit edbd56472a63 ("scsi: qla2xxx:
qla2x00_alloc_fw_dump: set ha->eft"). I think it should be included to 5.3 if
possible. It can be cherry-picked cleanly to master.
The logs of 5.3-rc8 (bad.log) and 5.3-rc8 with edbd56472a63 (good.log) are
applied.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2019-09-11 15:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 15:54 bugzilla-daemon [this message]
2019-09-11 15:55 ` [Bug 204815] qla2xxx: firmware is not responding to mailbox commands bugzilla-daemon
2019-09-11 15:57 ` bugzilla-daemon
2019-09-13 15:04 ` bugzilla-daemon
2019-09-13 16:03 ` bugzilla-daemon
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@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).