From: Hannes Reinecke <hare@suse.de>
To: james.smart@emulex.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 14/21] lpfc: Fix premature release of rpi bit in bitmask
Date: Fri, 10 Apr 2015 08:18:35 +0200 [thread overview]
Message-ID: <55276B3B.7000806@suse.de> (raw)
In-Reply-To: <1428095550.6933.42.camel@myfc17>
On 04/03/2015 11:12 PM, James Smart wrote:
> Fix premature release of rpi bit in bitmask
>
> Currently, the driver plays off the fact that older sli4 adapters have a
> different rpi access pattern that allowed for the rpi reference to be
> released earlier in the teardown sequence, allowing the driver to recycle
> the rpi value sooner. Newer sli4 adapters have a different access pattern that
> requires us to wait for a later mailbox completion. This changes the put
> call location on the newer sli4 adapters.
>
> Symptoms of the error are "0110 ELS" and the "0372 iotag" errors.
>
> Signed-off-by: Dick Kennedy <dick.kennedy@emulex.com>
> Signed-off-by: James Smart <james.smart@emulex.com>
> ---
Reviewed-by: Hannes Reinecke <hare@suse.de>
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-04-10 6:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-03 21:12 [PATCH 14/21] lpfc: Fix premature release of rpi bit in bitmask James Smart
2015-04-10 6:18 ` Hannes Reinecke [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-02-05 19:25 James Smart
2015-03-07 17:11 ` James Bottomley
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=55276B3B.7000806@suse.de \
--to=hare@suse.de \
--cc=james.smart@emulex.com \
--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).