DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shaham Fridenberg <ShahamF@Radware.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] dpdk 2.1.0: 40gig ports link is down
Date: Mon, 12 Oct 2015 17:04:01 +0000	[thread overview]
Message-ID: <2E654B490240B7449C846A96A8D8FE0CC439DF82@ILMB2.corp.radware.com> (raw)
In-Reply-To: <20151012083850.46f787a0@urahara>

Hey Stephen,

Thanks for your help.

I tried updating i40e driver to the latest version (from 1.0.11-k to 1.3.39.1) but it didn't help.

By 'Compile i40e with DEBUG flag' you mean adding "CONFIG_RTE_LOG_LEVEL=8" to defconfig_x86_64-wsm-linuxapp-gcc (assuming I'm compiling for westmere)?

Also, is there any log file generated in that case?

Thanks,
Shaham

-----Original Message-----
From: Stephen Hemminger [mailto:stephen@networkplumber.org] 
Sent: Monday, October 12, 2015 6:39 PM
To: Shaham Fridenberg
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] dpdk 2.1.0: 40gig ports link is down

On Mon, 12 Oct 2015 13:29:42 +0000
Shaham Fridenberg <ShahamF@Radware.com> wrote:

> Hey all,
> 
> I upgraded from dpdk 1.8.0 to 2.1.0 and now my 40gig ports (rte_i40e_pmd) link is down.
> 
> Any idea what might be the issue?
> 
> Thanks,
> Shaham

Compile i40e with DEBUG flag enabled in config and make sure LOGLEVEL is set to 8 to show debug output.

It maybe something related to firmware versions.
Make sure you have updated firmware (see Intel tool).

  reply	other threads:[~2015-10-12 17:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-12 13:29 Shaham Fridenberg
2015-10-12 15:38 ` Stephen Hemminger
2015-10-12 17:04   ` Shaham Fridenberg [this message]
2015-10-12 17:14     ` Stephen Hemminger
2015-10-13 11:57       ` Shaham Fridenberg

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=2E654B490240B7449C846A96A8D8FE0CC439DF82@ILMB2.corp.radware.com \
    --to=shahamf@radware.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.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).