From: Rui Xiang <rui.xiang@huawei.com>
To: <devel@open-fcoe.org>
Cc: <linux-kernel@vger.kernel.org>, <wuyanjiang@huawei.com>,
<jianghongbin@huawei.com>, <wick.wei@huawei.com>
Subject: A problem about OX_ID reused by FCoE driver
Date: Fri, 24 Jul 2015 11:52:38 +0800 [thread overview]
Message-ID: <55B1B686.8010006@huawei.com> (raw)
From: Wu Yanjiang <wuyanjiang@huawei.com>
Hi all,
On a system that was running 3.0.13-0.27-default, a problem that the OX_ID is reused by FCoE driver occurred.
Which can be confirmed is that the problem is occurred at initiator side, but the reason how does it happen is unknown.
By the trace captured by JDSU protocol analyzer, the initiator initiated a read command about 10 seconds after
the virtual link resumed . But about 10ms later, the initiator send ABTS to abort the read command. Then the
OX_ID was reused for a new command immediately without abort response from target side and RRQ process.
Test environment :
Initiator OS: SLES 11 SP2 (3.0.13-0.27-default)
Initiator CNA: INTEL X520-SR2
Test step:
1.INTEL X520-SR2 connect to intel 82599 card in target directly
2.Initiator initiates write and read command to target by FCoE VN2VN protect
3.Disconnect the physical link then reconnect it
Any advice is welcome.
Thanks.
reply other threads:[~2015-07-24 3:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=55B1B686.8010006@huawei.com \
--to=rui.xiang@huawei.com \
--cc=devel@open-fcoe.org \
--cc=jianghongbin@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wick.wei@huawei.com \
--cc=wuyanjiang@huawei.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