From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx03b-out01ag.rit.edu (mx03b-out01ag.rit.edu [129.21.3.135]) by dpdk.org (Postfix) with ESMTP id AB9F316E for ; Mon, 11 Dec 2017 22:24:21 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=rit.edu; i=@rit.edu; q=dns/txt; s=rit1608; t=1513027462; x=1544563462; h=mime-version:in-reply-to:references:date:message-id: subject:to:cc:reply-to:from; bh=/92U5cnbR9of8rTyc18NFphjAxNI1OMXYJBU2VNmClk=; b=mstDNp7a2QUkbZI3n8Sm9fQQcC4fd6aQR3n0euaXi2mqlxP/OjjHTIv1 vHpxcG3adfYeo04yJnWXLiA6tpybwiVmGcGtlxljahqdPHYXMyIfUgkFq cEPdtcDcJqoVk54HEKtZR4J4m/1ASNdMgfg7OIDNolnzQ2FsKzSsfQbBZ c=; From: Pragash Vijayaragavan X-IronPort-AV: E=Sophos;i="5.45,393,1508817600"; d="scan'208,217";a="164356571" Received: from mail-vk0-f72.google.com ([209.85.213.72]) by smtp-server.rit.edu with ESMTP/TLS/AES128-GCM-SHA256; 11 Dec 2017 16:24:21 -0500 Received: by mail-vk0-f72.google.com with SMTP id h203so10103375vka.12 for ; Mon, 11 Dec 2017 13:24:20 -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=L3xrfb87zAEyTIbiMUEFP5mW9wmtYxP9gKwAWCHA9dg=; b=AFps/6fqcn1WS7kOWuSCjwCc/RhBTgm6fUj0bMuR4+jyCRg1ZHMIJyBESsCHVXdD5M QgGP0ORNPqNdMeu8gVxlBnKmfik1OdEeMw+SrbaAWHrqZdQit3BXP5MqWyAUX+JwYfa1 Pv+e+nG1RWSLBoE+5lh3T1P3SQvimrCC1vb+yLxu4jPSCznIfuBgl3uP2tlWo71eLF7b zcCm1/vEUESfc7O/OBA6Q4VwHi1SnDEAjDNzhCecCtJgzZD8aQzPicewEoz3zUlR+jQd b1a72Zkq3ov9T0gU9DMSdxhQgoE3WXtE9PncvAR9yyyv1UZSYWYYOmM66plOPb0ccug2 zHmA== X-Gm-Message-State: AKGB3mIIFrRTcdW3Y5GZqZibRXNMdi34lNKeHdX7zt9tIzhBcvMSN7nF kJdeLIgLYBVt5rBYlJPRmsKkK0tAabbCM1cj+iVE1XKE/FUSoiLI5spJ0zrD5lRJip0L/mKf0P7 dSl9kAFdBqO7P8w4vmjp/X8ibqt9zhxsQ X-Received: by 10.176.3.50 with SMTP id 47mr2044895uat.193.1513027459999; Mon, 11 Dec 2017 13:24:19 -0800 (PST) X-Google-Smtp-Source: ACJfBovedxS7D77WtgptizvA8alFZBVsE8VY/P9jTDAZwDC1fa7/ygHMNCQD0+xlphl6YDklJVU6ZSkyKHffaubVANU= X-Received: by 10.176.3.50 with SMTP id 47mr2044873uat.193.1513027459700; Mon, 11 Dec 2017 13:24:19 -0800 (PST) MIME-Version: 1.0 Received: by 10.176.76.81 with HTTP; Mon, 11 Dec 2017 13:24:18 -0800 (PST) In-Reply-To: References: Date: Mon, 11 Dec 2017 16:24:18 -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: Mon, 11 Dec 2017 21:24:22 -0000 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 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. >