From: ankit kumar <akprajapati616@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] could nvm_checksum_validate Error may cause non-functioning of DPDK.
Date: Thu, 14 Nov 2013 11:03:45 +0530 [thread overview]
Message-ID: <CAG9qd2rM+gvBzGLYECtY83Aj7hMyhBS0zNwj9Yu05huv1xuX5w@mail.gmail.com> (raw)
Hi,
I am trying to work on DPDK-1.5.0r0 with intel i350 dual port NIC
with intel i3 processor on Fedora 18 (kernel-3.11.4). But after
building dpdk when i try to run testpmd application its not working
with some error as...
"EAL: Ask a virtual area of 0x2097152 bytes
EAL: Virtual area found at 0x7faddaa00000 (size = 0x200000)
EAL: Requesting 128 pages of size 2MB from socket 0
EAL: TSC frequency is ~3300000 KHz
EAL: Master core 0 is ready (tid=ec6e3880)
EAL: Core 1 is ready (tid=da1fe700)
EAL: PCI device 0000:01:00.0 on NUMA socket -1
EAL: probe driver: 8086:1521 rte_igb_pmd
EAL: PCI memory mapped at 0x7fadec07e000
EAL: PCI memory mapped at 0x7fadec6f1000
EAL: PCI device 0000:01:00.1 on NUMA socket -1
EAL: probe driver: 8086:1521 rte_igb_pmd
EAL: PCI memory mapped at 0x7fadeb900000
EAL: PCI memory mapped at 0x7fadec6ed000
EAL: Error - exiting with code: 1
Cause: No probed ethernet devices - check that
CONFIG_RTE_LIBRTE_IGB_PMD=y and that CONFIG_RTE_LIBRTE_EM_PMD=y and
that CONFIG_RTE_LIBRTE_IXGBE_PMD=y in your configuration file
"
When i searched for kernel logs, it shows me as NVM_CHECKSUM_INVALID
for this NIC. As per my knowledge its a EEPROM error in NIC card. So
to work around it i changed the driver code given in dpdk-1.5.0r0 in
dpdk-1.5.0r1/lib/librte_eal/linuxapp/kni/ethtool/igb/e1000_nvm.c to
just return the success messages whenever anyone ask for
nvm_checksum_validate.
But still its not working & showing the above logs. Please help.
Thanx.
next reply other threads:[~2013-11-14 5:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 5:33 ankit kumar [this message]
2013-11-14 10:04 ` Thomas Monjalon
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=CAG9qd2rM+gvBzGLYECtY83Aj7hMyhBS0zNwj9Yu05huv1xuX5w@mail.gmail.com \
--to=akprajapati616@gmail.com \
--cc=dev@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).