From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Daniel Wagner <dwagner@suse.de>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
Nilesh Javali <njavali@marvell.com>,
Martin Wilck <mwilck@suse.com>, Arun Easi <aeasi@marvell.com>
Subject: Re: [PATCH v3 0/4] qla2xxx: A couple crash fixes
Date: Wed, 09 Sep 2020 22:12:25 -0400 [thread overview]
Message-ID: <yq1lfhi2xdv.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20200908081516.8561-1-dwagner@suse.de> (Daniel Wagner's message of "Tue, 8 Sep 2020 10:15:12 +0200")
Daniel,
> The first crash we observed is due memory corruption in the srb memory
> pool. Unforuntatly, I couldn't find the source of the problem but the
> workaround by resetting the cleanup callbacks 'fixes' this problem
> (patch #1). I think as intermeditate step this should be merged until
> the real cause can be identified.
>
> The second crash is due a race condition(?) in the firmware. The sts
> entries are not updated in time which leads to this crash pattern
> which several customers have reported:
Applied to 5.10/scsi-staging. Thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2020-09-10 2:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 8:15 [PATCH v3 0/4] qla2xxx: A couple crash fixes Daniel Wagner
2020-09-08 8:15 ` [PATCH v3 1/4] qla2xxx: Warn if done() or free() are called on an already freed srb Daniel Wagner
2020-09-08 8:15 ` [PATCH v3 2/4] qla2xxx: Simplify return value logic in qla2x00_get_sp_from_handle() Daniel Wagner
2020-09-08 8:15 ` [PATCH v3 3/4] qla2xxx: Log calling function name " Daniel Wagner
2020-09-08 8:15 ` [PATCH v3 4/4] qla2xxx: Handle incorrect entry_type entries Daniel Wagner
2020-09-09 22:38 ` [EXT] [PATCH v3 0/4] qla2xxx: A couple crash fixes Arun Easi
2020-09-10 2:12 ` Martin K. Petersen [this message]
2020-09-15 20:16 ` Martin K. Petersen
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=yq1lfhi2xdv.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=aeasi@marvell.com \
--cc=dwagner@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mwilck@suse.com \
--cc=njavali@marvell.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;
as well as URLs for NNTP newsgroup(s).