From: Upendra Pathrikar <uspathrikar@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] Issue with error EAL: Error reading from file descriptor 21: Input/output error
Date: Fri, 6 May 2016 13:28:22 +0530 [thread overview]
Message-ID: <CAGSHHKcoE8_ryRhioCnfDu52yGeJM+VGpOLfbKGazmype1MJrQ@mail.gmail.com> (raw)
Hi,
I am using machine with
on board NIC - pci-e connection - Intel Corporation Ethernet Connection
I217-LM (rev 04) -e1000e kernel deriver
add on card - pci conncetion - Intel Corporation 82540EM Gigabit Ethernet
Controller (rev 02) -e1000 kernel driver
whenever i bind only I217-LM with igb_uio, testpmd($ sudo ./testpmd -c 0xff
-n 4 -- -i) runs well without any error and pmd identify port and
everything.
but whenever i bind 82540EM with igb_uio, testpmd($ sudo ./testpmd -c 0xff
-n 4 -- -i) runs with error "EAL: Error reading from file descriptor 21:
Input/output error" though it runs and identify port etc. But continues
"EAL: Error reading from file descriptor 21: Input/output error" is printed
on screen.
So is this error specfic to nic or driver e1000 or pci connection ?
I am unable to identify. If i add one more card of Intel Corporation
82540EM Gigabit Ethernet Controller (rev 02) -e1000 kernel driver with pci
connection, now it gives two errors "EAL: Error reading from file
descriptor 21: Input/output error" and "EAL: Error reading from file
descriptor 23: Input/output error" one after another in continues stream
I tried for dpdk-2.0.0, dpdk-2.2.0 and dpdk-16.04
What is exact problem behind error and how can we resolve this.
--
*Regards,Upendra Sunil PathrikarBharti School of Telecom Technology and
Management,Indian Institute of Technology, Delhi.*
next reply other threads:[~2016-05-06 7:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-06 7:58 Upendra Pathrikar [this message]
2016-05-06 8:25 ` SAKTHIVEL ANAND S
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=CAGSHHKcoE8_ryRhioCnfDu52yGeJM+VGpOLfbKGazmype1MJrQ@mail.gmail.com \
--to=uspathrikar@gmail.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).