From: Stephen Hemminger <stephen@networkplumber.org>
To: Masaru Oki <m-oki@stratosphere.co.jp>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] EAL : Input/output error on DPDK 1.7.1
Date: Fri, 24 Oct 2014 14:51:09 +0530 [thread overview]
Message-ID: <CAOaVG178TDLvbzi00LaqQoH2e8JbhEH3OP4T-V4aCCcaXpN_gg@mail.gmail.com> (raw)
In-Reply-To: <CAFLKUz+p2zez0yLPgvQSeg+A=0KHUamccOJAK0wL_CDDe6=noA@mail.gmail.com>
INTX is badly emulated in VMWare; the disable logic doesn't work.
I thought the DPDK API detected when link state interrupt would not work.
But of course the application needs to check that before enabling link state
On Fri, Oct 24, 2014 at 8:52 AM, Masaru Oki <m-oki@stratosphere.co.jp>
wrote:
> Hi,
> I got same result in VMware Workstation environment.
> At least in my environment, INTX toggle check is not work with VMware
> E1000 Ethernet.
> Please try attached patch.
>
> 2014-10-17 3:04 GMT+09:00 Raghav K <rghvk@outlook.com>:
> > Hey,
> > I observe continuous burst of I/O Errors, as indicated below, with the
> testpmd application with DPDK 1.7.1.This seems to originate from
> eal_intr_process_interrupts() function. I seemed to have setup the DPDK
> prerequisites alright.
> > Another recent post seemed to suggest moving back to 1.7.0, however I
> would like to persist with 1.7.1.
> > Any help/pointers in resolving this would be greatly appreciated.
> > Much thanks,Raghav
> > root@sys6-vm6:/home/rghv/dpdk/dpdk-1.7.1/x86_64-native-linuxapp-gcc/app#
> ./testpmd -c 0xf -n3 -- -i --nb-cores=3 --nb-ports=2
> > EAL: Error reading from file descriptor 21: Input/output errorEAL: Error
> reading from file descriptor 21: Input/output errorEAL: Error reading from
> file descriptor 21: Input/output errorEAL: Error reading from file
> descriptor 21: Input/output errorEAL: Error reading from file descriptor
> 21: Input/output errorEAL: Error reading from file descriptor 21:
> Input/output errorEAL: Error reading from file descriptor 21: Input/output
> errorEAL: Error reading from file descriptor 21: Input/output errorEAL:
> Error reading from file descriptor 21: Input/output errorEAL: Error reading
> from file descriptor 21: Input/output errorEAL: Error reading from file
> descriptor 21: Input/output errorEAL: Error reading from file descriptor
> 21: Input/output errorEAL: Error reading from file descriptor 21:
> Input/output errorEAL: Error reading from file descriptor 21: Input/output
> errorEAL: Error reading from file descriptor 21: Input/output errorEAL:
> Error reading from file descriptor 21: Input/output error
> > ----
> > root@sys6-vm6:/home/rghv/dpdk/dpdk-1.7.1# ./tools/dpdk_nic_bind.py
> --status
> > Network devices using DPDK-compatible
> driver============================================0000:02:01.0 '82545EM
> Gigabit Ethernet Controller (Copper)' drv=igb_uio unused=e10000000:02:02.0
> '82545EM Gigabit Ethernet Controller (Copper)' drv=igb_uio unused=e1000
> > Network devices using kernel
> driver===================================0000:02:00.0 '82545EM Gigabit
> Ethernet Controller (Copper)' if=eth0 drv=e1000 unused=igb_uio
> *Active*0000:02:03.0 '82545EM Gigabit Ethernet Controller (Copper)' if=eth3
> drv=e1000 unused=igb_uio 0000:02:05.0 '82545EM Gigabit Ethernet Controller
> (Copper)' if=eth4 drv=e1000 unused=igb_uio 0000:02:06.0 '82545EM Gigabit
> Ethernet Controller (Copper)' if=eth5 drv=e1000 unused=igb_uio
> > Other network devices=====================<none>
>
prev parent reply other threads:[~2014-10-24 9:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 18:04 Raghav K
2014-10-24 3:22 ` Masaru Oki
2014-10-24 9:21 ` Stephen Hemminger [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=CAOaVG178TDLvbzi00LaqQoH2e8JbhEH3OP4T-V4aCCcaXpN_gg@mail.gmail.com \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=m-oki@stratosphere.co.jp \
/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).