From: Daniel Waddington <Daniel.Waddington@ibm.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: Re: IOAT channel halting unexpectedly
Date: Tue, 14 Jun 2022 23:14:58 +0000 [thread overview]
Message-ID: <SJ0PR15MB4421BB5851C7430566D96633F5AA9@SJ0PR15MB4421.namprd15.prod.outlook.com> (raw)
In-Reply-To: <SJ0PR15MB4421B108339518692B018338F5AA9@SJ0PR15MB4421.namprd15.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]
I think I just answered my own question – too large a transfer size is the cause.
Daniel
From: Daniel Waddington <Daniel.Waddington@ibm.com>
Date: Tuesday, June 14, 2022 at 3:17 PM
To: users@dpdk.org <users@dpdk.org>
Subject: [EXTERNAL] IOAT channel halting unexpectedly
Hi DPDK folks, I’m trying to use IOAT (rte_dma_copy) on Skylake. I can do a single submit and completion OK. When I try to do more (> 3 as it happens), the IOAT reports: “ioat_completed(): Device HALTED and could not be recovered”.
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
ZjQcmQRYFpfptBannerEnd
Hi DPDK folks,
I’m trying to use IOAT (rte_dma_copy) on Skylake. I can do a single submit and completion OK. When I try to do more (> 3 as it happens), the IOAT reports:
“ioat_completed(): Device HALTED and could not be recovered”.
From the rte_dma_dump I see the channel status has entered HALTED and the completions stop.
My question is, what can cause the channel to halt? (e.g. bad src or dst address). Any hints on how I might debug this?
Also, I have to reboot to get it out of this state. Re-loading drivers doesn’t seem to help – any other way?
Daniel
[-- Attachment #2: Type: text/html, Size: 4803 bytes --]
prev parent reply other threads:[~2022-06-14 23:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 22:17 Daniel Waddington
2022-06-14 23:14 ` Daniel Waddington [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=SJ0PR15MB4421BB5851C7430566D96633F5AA9@SJ0PR15MB4421.namprd15.prod.outlook.com \
--to=daniel.waddington@ibm.com \
--cc=users@dpdk.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).