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: Wed, 15 Jul 2020 15:44:47 +0000 [thread overview]
Message-ID: <A19A9FEB-37EE-458D-8B54-DCD43B8AB7A4@intel.com> (raw)
In-Reply-To: 20200715024918.31655.31915@ml01.vlan13.01.org
[-- Attachment #1: Type: text/plain, Size: 2399 bytes --]
Hi Jiahao,
I don't know off the top of my head but I can try and repro with one of the SPDK tools and see what I can see. In the meantime you can try "/scripts/setup.sh reset" followed by setup.sh again to see if that gives you a temp workaround
Thx
Paul
On 7/14/20, 7:49 PM, "lijh2015(a)mail.ustc.edu.cn" <lijh2015(a)mail.ustc.edu.cn> wrote:
Hi SPDK team,
I'm using SPDK (v20-01-pre) to evaluate I/OAT performance. There are some bugs in my benchmark program,
but after I use ctrl+c to quit my program and restart it again, some error messages appeared:
ioat.c: 480:ioat_channel_start: *ERROR*: could not start channel: status = 0x3
error = 0
ioat.c: 547:ioat_enum_cb: *ERROR*: ioat_attach() failed
EAL: Requested device 0000:00:04.0 cannot be used
ioat.c: 480:ioat_channel_start: *ERROR*: could not start channel: status = 0x3
error = 0
ioat.c: 547:ioat_enum_cb: *ERROR*: ioat_attach() failed
EAL: Requested device 0000:00:04.1 cannot be used
ioat.c: 480:ioat_channel_start: *ERROR*: could not start channel: status = 0x3
error = 0
ioat.c: 547:ioat_enum_cb: *ERROR*: ioat_attach() failed
EAL: Requested device 0000:00:04.2 cannot be used
ioat.c: 480:ioat_channel_start: *ERROR*: could not start channel: status = 0x3
error = 0
ioat.c: 547:ioat_enum_cb: *ERROR*: ioat_attach() failed
EAL: Requested device 0000:00:04.3 cannot be used
ioat.c: 480:ioat_channel_start: *ERROR*: could not start channel: status = 0x3
error = 0
ioat.c: 547:ioat_enum_cb: *ERROR*: ioat_attach() failed
EAL: Requested device 0000:40:04.0 cannot be used
ioat.c: 480:ioat_channel_start: *ERROR*: could not start channel: status = 0x3
error = 0
ioat.c: 547:ioat_enum_cb: *ERROR*: ioat_attach() failed
EAL: Requested device 0000:40:04.1 cannot be used
ioat.c: 480:ioat_channel_start: *ERROR*: could not start channel: status = 0x3
error = 0
I checked the code in lib/ioat/ioat.c, it seems is_ioat_idle always returns negative results.
What should I do to deal with this problem without rebooting my server? Or, at least,
how to prevent it?
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-15 15:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 15:44 Luse, Paul E [this message]
2020-07-16 11:23 [SPDK] Re: ioat: "could not start channel" after abnormal exit lijh2015
2020-07-16 14:28 Luse, Paul E
2020-07-16 18:20 lijh2015
2020-07-16 18:36 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=A19A9FEB-37EE-458D-8B54-DCD43B8AB7A4@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.