From: Bart Van Assche <bvanassche-HInyCGIudOg@public.gmane.org>
To: Roland Dreier <roland-BHEL68pLQRGGvPXPguhicg@public.gmane.org>
Cc: Alexey Shvetsov <alexxy-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: kernel: rejected SRP_LOGIN_REQ because creating a new RDMA channel failed.
Date: Thu, 19 Apr 2012 06:41:26 +0000 [thread overview]
Message-ID: <4F8FB396.6010200@acm.org> (raw)
In-Reply-To: <CAL1RGDXCtfK8L_Gt2BWwYWKySMjMY6sS8eOzUJXe9S6UW9Qkkw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 04/18/12 20:21, Roland Dreier wrote:
> On Wed, Apr 18, 2012 at 2:07 AM, Alexey Shvetsov <alexxy-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org> wrote:
>> Apr 18 13:04:01 store kernel: mlx4_core 0000:4b:00.0: command 0x19 failed: fw status = 0x9
>
> status 0x9 is:
>
> /* Resource is not in the appropriate state or ownership: */
> CMD_STAT_BAD_RES_STATE = 0x09,
>
> Bart, I seem to remember you had tracked this down to a bug in the SRPT code?
ib_destroy_cm_id() must be invoked before srpt_destroy_ch_ib() otherwise
srpt_ch_qp_err() can get invoked after a QP has already been freed and
reused. The patch that fixes this issue for the SCST version of ib_srpt
can be found here:
http://scst.svn.sourceforge.net/viewvc/scst?view=revision&revision=4139.
Bart.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-04-19 6:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 9:07 kernel: rejected SRP_LOGIN_REQ because creating a new RDMA channel failed Alexey Shvetsov
[not found] ` <105692b8ae6e4f11fae2848be32f88d7-heEE5zn7HfaV8fSEjHp0FA@public.gmane.org>
2012-04-18 20:21 ` Roland Dreier
[not found] ` <CAL1RGDXCtfK8L_Gt2BWwYWKySMjMY6sS8eOzUJXe9S6UW9Qkkw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-04-19 6:41 ` Bart Van Assche [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=4F8FB396.6010200@acm.org \
--to=bvanassche-hinycgiudog@public.gmane.org \
--cc=alexxy-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=roland-BHEL68pLQRGGvPXPguhicg@public.gmane.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