Re: Intel 82571EB PMD support

Hi Stefan,

It will be of great help if you or anyone else could help me resolve this issue.

I have checked 82571EB on following setup:

OS version: CentOS 6.4 [ kernel 2.6.32.358 ]
DPDK version : DPDK 1.6.0-r1

Let me know if any update of centos can help resolve this issue?


Thanks & Regards
Chetan Bali
________________________________________
From: Stefan Baranoff [sbaranoff-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org]
Sent: Sunday, March 09, 2014 7:39 PM
To: Chetan Bali
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: [dpdk-dev] Intel 82571EB PMD support

Chetan,

I saw exactly that behavior with an 82599EB but running DPDK version 1.3.2 and CentOS 6.2 and the fix for me was upgrading to CentOS 6.4 - there was a thread a while back about a bug that caused DD to not be set but I can't seem to find it right now.

I'm sorry I can't be of more help but at least this is a symptom that has been seen before.

Regards,
Stefan

Sent from my smart phone; people don't make typos, Swype does!

On Mar 7, 2014 5:18 AM, "Chetan Bali" <chetan.bali-pccXkzZloW5BDgjK7y7TUQ@public.gmane.org<mailto:chetan.bali-pccXkzZloW5BDgjK7y7TUQ@public.gmane.org>> wrote:
Hi,

Do we have PMD support for intel 82571EB. We are having e1000e driver supported for 82571EB in linux.

DPDK Version : 1.6.0-r1

Linux Kernel : CentOS 6.4 [ kernel version 2.6.32-358.el6.x86_64 ]


Issue:

When we run DPDK example [ l2fwd ], we are able to see successful init of rte_pmd_em and link is also detected successfully.
But the RX, TX count are zero. If we try to fetch nic stats using rte_eth_stats_get(), we can see around 256 ipacket count but after that error count [rx error ] starts increasing.

We are not able to see any packet on user app [ l2fwd ]. Does anyone else face the same issue?

Regards
Chetan Bali




===============================================================================
Please refer to http://www.aricent.com/legal/email_disclaimer.html
for important disclosures regarding this electronic communication.
===============================================================================




===============================================================================
Please refer to http://www.aricent.com/legal/email_disclaimer.html
for important disclosures regarding this electronic communication.
===============================================================================