From: Luse, Paul E <paul.e.luse at intel.com>
To: spdk@lists.01.org
Subject: [SPDK] Re: ioat: "could not start channel" after abnormal exit
Date: Thu, 16 Jul 2020 14:28:21 +0000 [thread overview]
Message-ID: <180EC04F-A8F0-4F26-8A7A-77879526E14D@intel.com> (raw)
In-Reply-To: 20200716112305.31655.99698@ml01.vlan13.01.org
[-- Attachment #1: Type: text/plain, Size: 2950 bytes --]
Hi Jiahao,
Well that’s good news. I did try ctrl-c exit from both ioat_perf and the new accel_perf that I'm working on now and they both worked fine. BTW, accel_perf is being developed as the perf tool for the new (renamed and expanded) acceleration framework that you might be interested in. It's not quite feature complete yet but for the upcoming release in just a few weeks the accel framework will include support for IOAT, DSA (next gen IOAT not yet available in Si but once it is it will be a huge performance boost, plus new features) as well as sw implementations for all the features so that the framework API can be used in any environment. Let me know if you'd like more info on any of that.
Now, wrt your IOAT issue, are you saying that following simply using a bogus address in a command that you're in a state where powering down the machine and powering it that some channels are still bad? Please confirm, that sounds "odd" for sure. Also please confirm that you power cycled, not just rebooted.
Thx
Paul
On 7/16/20, 4:23 AM, "lijh2015(a)mail.ustc.edu.cn" <lijh2015(a)mail.ustc.edu.cn> wrote:
Hi Paul,
Thanks for your advice. But that didn't seem to work. The output of /scripts/setup.sh is same as normal
In fact, I found out how such error happens. It's because I accidentally launch ioat copy
on system malloc-ed memory space, I've already fixed that in my code. But there are still some
errors around. After reboot, and run scripts/setup.sh again, there are still 4 channels (1 channel
from each process) cannot be attached:
E0716 19:02:24.496325 189532 ioat.c:480] [SPDK/ioat_channel_start] could not start channel: status = 0x3
error = 0
E0716 19:02:24.496567 189532 ioat.c:547] [SPDK/ioat_enum_cb] ioat_attach() failed
EAL: Requested device 0000:00:04.4 cannot be used
E0716 19:02:24.527472 189532 ioat.c:480] [SPDK/ioat_channel_start] could not start channel: status = 0x3
error = 0
E0716 19:02:24.527948 189532 ioat.c:547] [SPDK/ioat_enum_cb] ioat_attach() failed
EAL: Requested device 0000:40:04.4 cannot be used
E0716 19:02:24.558609 189532 ioat.c:480] [SPDK/ioat_channel_start] could not start channel: status = 0x3
error = 0
E0716 19:02:24.559036 189532 ioat.c:547] [SPDK/ioat_enum_cb] ioat_attach() failed
EAL: Requested device 0000:80:04.4 cannot be used
E0716 19:02:24.589241 189532 ioat.c:480] [SPDK/ioat_channel_start] could not start channel: status = 0x3
error = 0
E0716 19:02:24.589682 189532 ioat.c:547] [SPDK/ioat_enum_cb] ioat_attach() failed
EAL: Requested device 0000:c0:04.4 cannot be used
The other channels are working fine now, but these errors are strange.
Thanks,
Jiahao Li
_______________________________________________
SPDK mailing list -- spdk(a)lists.01.org
To unsubscribe send an email to spdk-leave(a)lists.01.org
next reply other threads:[~2020-07-16 14:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 14:28 Luse, Paul E [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-07-16 18:36 [SPDK] Re: ioat: "could not start channel" after abnormal exit Luse, Paul E
2020-07-16 18:20 lijh2015
2020-07-16 11:23 lijh2015
2020-07-15 15:44 Luse, Paul E
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=180EC04F-A8F0-4F26-8A7A-77879526E14D@intel.com \
--to=spdk@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.