From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx03a-out01ag.rit.edu (mx03a-out01ag.rit.edu [129.21.3.134]) by dpdk.org (Postfix) with ESMTP id B7710239 for ; Tue, 12 Dec 2017 07:17:04 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=rit.edu; i=@rit.edu; q=dns/txt; s=rit1608; t=1513059426; x=1544595426; h=mime-version:in-reply-to:references:date:message-id: subject:to:cc:reply-to:from; bh=QVg56Zw2PKxxg0LUrAbZ0nf7Il5u71vs/0l87Zf7TMs=; b=YMTWxlxzTpaKgGNRq4+nm/hEYl5EqJiyjgRTN3V/yUxxGH6adONAnKmb bHx4Lx/V4h0pS9vrNmff/ulTztR8NntWJBsz/VfEZLUHVh6Xl6IEMC/4X WmcnXekhozNR8Hk85K1Vs5NgMe3pWXhcOeFeW7LeVH6iSUo4Y4rKZIn2I 4=; From: Pragash Vijayaragavan X-IronPort-AV: E=Sophos;i="5.45,394,1508817600"; d="scan'208,217";a="162803696" Received: from mail-vk0-f70.google.com ([209.85.213.70]) by smtp-server.rit.edu with ESMTP/TLS/AES128-GCM-SHA256; 12 Dec 2017 01:17:04 -0500 Received: by mail-vk0-f70.google.com with SMTP id w136so10872992vkd.14 for ; Mon, 11 Dec 2017 22:17:03 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=jSSA3ldgog9LwjgkB9q+O/5qOslDssJTrkYtIidSvPk=; b=uBuoeqQUTPq8/1hfCIHGKwwYF30F5aUfZzBrVm9qfhSgclz3GxMue2w2od6sg9nCaR lP2F72LXuzqbmnMSI/bxTKcREsUMNKclDyHXqTEsPGblc8ApORwWt7f57nr+GMMZlEUO dfom/Ir8giEn3yPuIsjT4jgG4BT4R7Aw00UIhWna+QKPQwbq6kuYzYfm5qzcXBRJ+IL/ iPXnyPxImTeTPSPeiS+c4iQ3u8ubxPqoGaZpRfBsxyJXd/tiwGkad875frR6OARhehal RCBOP33onoALMG6eYtHBNfAqWt3VhIm5Z4TySsJXYCwDu+n5BjWy+x00sJYxqyHOUcz5 lfbw== X-Gm-Message-State: AKGB3mJBkCYEdYZBWl9WE5Lvsc3TtOTNHOb1HQiBOdatZCrjKuMAjaIj B3LduWw5ChklNcVJXM1Xq0aCXlsKKVUaaFtHVQa4p2ydRkyY+3y5utdjbugODrUmykjm9asnrJp aQW9XuCyqAunaFK5E3KUF1zYt6RHFXcqd X-Received: by 10.31.52.196 with SMTP id b187mr2902028vka.23.1513059422774; Mon, 11 Dec 2017 22:17:02 -0800 (PST) X-Google-Smtp-Source: ACJfBos0nd+Pk+9tpalcBVAG5ieTrF6m4xddblHfsvePpafV59UIvwDsihSwJjKOkuzEsVMil2cAMahcQfNaz4PaY2Q= X-Received: by 10.31.52.196 with SMTP id b187mr2902009vka.23.1513059422475; Mon, 11 Dec 2017 22:17:02 -0800 (PST) MIME-Version: 1.0 Received: by 10.176.76.81 with HTTP; Mon, 11 Dec 2017 22:17:01 -0800 (PST) In-Reply-To: References: Date: Tue, 12 Dec 2017 01:17:01 -0500 Message-ID: To: "Hristo.Trifonov" Cc: "users@dpdk.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-users] port 0 not present on board error X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: pxv3620@rit.edu List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Dec 2017 06:17:05 -0000 I tried to debug by printing the check_port_config function and printed the nb_ports parameter, -> this is 0 so i guess no ports are bind to the dpdk driver since its still showing net_i40e in probe driver. Should i do any config to solve this error. i am using igb_uio and the ports are bind correctly, i bind using the dpdk_dev_bind script. pragash@revvit:~/dpdk-stable-17.05.2/examples/l3fwd/build$ ./l3fwd -l 1-19 --no-huge -- -p 0x07 -L --config="(0,0,1),(1,0,2)" --ipv6 --parse-ptype EAL: Detected 20 lcore(s) EAL: Probing VFIO support... EAL: Started without hugepages support, physical addresses not available EAL: PCI device 0000:02:00.0 on NUMA socket 0 EAL: probe driver: 8086:1583 net_i40e EAL: Requested device 0000:02:00.0 cannot be used EAL: PCI device 0000:02:00.1 on NUMA socket 0 EAL: probe driver: 8086:1583 net_i40e EAL: PCI device 0000:04:00.0 on NUMA socket 0 EAL: probe driver: 8086:1583 net_i40e EAL: Requested device 0000:04:00.0 cannot be used EAL: PCI device 0000:04:00.1 on NUMA socket 0 EAL: probe driver: 8086:1583 net_i40e EAL: PCI device 0000:08:00.0 on NUMA socket 0 EAL: probe driver: 8086:1521 net_e1000_igb EAL: PCI device 0000:08:00.1 on NUMA socket 0 EAL: probe driver: 8086:1521 net_e1000_igb L3FWD: Longest-prefix match selected L3FWD: IPV6 is specifiednsoft parse-ptype is enabled ports ---- 0 port 0 is not present on the board EAL: Error - exiting with code: 1 Cause: check_port_config failed Thanks, Pragash Vijayaragavan Grad Student at Rochester Institute of Technology email : pxv3620@rit.edu ph : 585 764 4662 On Mon, Dec 11, 2017 at 4:24 PM, Pragash Vijayaragavan wrote: > Hi, > > I am still getting some errors; > > port 0 is not present on the board. > > pragash@revvit:~/dpdk-stable-17.05.2/examples/l3fwd/build$ ./l3fwd -l 1-4 > --no-huge -- -p 0x3 -L --config="(0,0,1),(1,0,2)" --ipv6 --parse-ptype > EAL: Detected 20 lcore(s) > EAL: Probing VFIO support... > EAL: Started without hugepages support, physical addresses not available > EAL: PCI device 0000:02:00.0 on NUMA socket 0 > EAL: probe driver: 8086:1583 net_i40e > EAL: Requested device 0000:02:00.0 cannot be used > EAL: PCI device 0000:02:00.1 on NUMA socket 0 > EAL: probe driver: 8086:1583 net_i40e > EAL: PCI device 0000:04:00.0 on NUMA socket 0 > EAL: probe driver: 8086:1583 net_i40e > EAL: Requested device 0000:04:00.0 cannot be used > EAL: PCI device 0000:04:00.1 on NUMA socket 0 > EAL: probe driver: 8086:1583 net_i40e > EAL: PCI device 0000:08:00.0 on NUMA socket 0 > EAL: probe driver: 8086:1521 net_e1000_igb > EAL: PCI device 0000:08:00.1 on NUMA socket 0 > EAL: probe driver: 8086:1521 net_e1000_igb > L3FWD: Longest-prefix match selected > L3FWD: IPV6 is specifiednsoft parse-ptype is enabled > port 0 is not present on the board > EAL: Error - exiting with code: 1 > Cause: check_port_config failed > > > Thanks, > > Pragash Vijayaragavan > Grad Student at Rochester Institute of Technology > email : pxv3620@rit.edu > ph : 585 764 4662 <(585)%20764-4662> > > > On Mon, Dec 11, 2017 at 6:21 AM, Hristo.Trifonov > wrote: > >> Not showing "Active" status is perfectly normal. >> >> The problem here is that you will probably need to supply extra >> parameters. >> This is from your previous posts: >> >> pragash at revvit:~/dpdk-stable-17.05.2/examples/l3fwd/build$ >> ./l3fwd -l 0-4 --no-huge -- -p 0x1 >> >> Try changing to: >> >> pragash at revvit:~/dpdk-stable-17.05.2/examples/l3fwd/build$ >> ./l3fwd -l 1-4(core 0 is usually master lcore) --no-huge -- -p 0x3 >> -L(optional) -config="(0,0,1),(1,0,2)" --parse-type >> >> >> >> This worked for me. You can check the docs here >> http://dpdk.org/doc/guides/sample_app_ug/l3_forward.html for all options. >> >> >> If you don't specify the "config" option the app won't even start >> returning the "check port config" error. You must also supply the >> "-parse-type" cmd parameter otherwise app complaints and fails to start >> with the following error "port 0 cannot parse packet type, please add >> -parse-type" >> >> Hristo T. >> > >