From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-f42.google.com (mail-pa0-f42.google.com [209.85.220.42]) by dpdk.org (Postfix) with ESMTP id BAE945AA2 for ; Thu, 22 Jan 2015 17:43:19 +0100 (CET) Received: by mail-pa0-f42.google.com with SMTP id bj1so1849707pad.1 for ; Thu, 22 Jan 2015 08:43:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Lsy8Ouwy59j5IbsmhAI2r5gJrrR9oiwsQ1FOYgZJ47I=; b=FjmQIIxIlk5D6jMC2yqmjp6fxprWWSl9ABjpB3vZEUEpzP6x5w1Omros58qEGR3QFN i7sCJLG9UkDq0q6Imp+uS4A18ESJQbKOQDqdZHThXt3BIjejt/kkQgnkLrMAPjInlSvP W3hDfh/uREfomCGdDeZZEWijfSqr54OxoLQDsuyVH9qIpgQt3WAN6eBpNDKftExlLqRz zq7cUCz2oqkGoipujhTI8KRtc/K4n7MzkHI+HVgntI+6hpD0Ixcne2vALVSWBf7ErLl9 R4YmVXDW2wXnlMpE48endDh48NKCgWcgle3BBaAI0umYkvPApwp4n1ZZzv+EoCfmgbal WZFQ== MIME-Version: 1.0 X-Received: by 10.68.194.106 with SMTP id hv10mr3757818pbc.50.1421944998977; Thu, 22 Jan 2015 08:43:18 -0800 (PST) Received: by 10.70.91.166 with HTTP; Thu, 22 Jan 2015 08:43:18 -0800 (PST) In-Reply-To: References: <533710CFB86FA344BFBF2D6802E60286CB7008@SHSMSX101.ccr.corp.intel.com> Date: Thu, 22 Jan 2015 08:43:18 -0800 Message-ID: From: Ravi Kerur To: "Qiu, Michael" , "Liu, Yong" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Cc: "dts@dpdk.org" Subject: Re: [dts] Clarifications on setting up DUT X-BeenThere: dts@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: test suite reviews and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2015 16:43:20 -0000 Hi Yong, Thanks, your changes worked on Ubuntu. Yong, Michael, I have sent out a patch to reduce errors logged in dts.log and I217/I218 support. please take a look at it and let me know your inputs. Thanks, Ravi On Mon, Jan 19, 2015 at 11:07 AM, Ravi Kerur wrote: > Hi Michael, > > I got 2 systems assembled which had I217 and I218 chipsets on the > motherboard and I was not quite satisfied with the testing I did to claim > support for these chipsets (primarily used testpmd for testing) so looked > at DTS to complement the testing I did. > > More Inline > > On Sun, Jan 18, 2015 at 5:19 PM, Qiu, Michael > wrote: > >> On 2015/1/17 5:09, Ravi Kerur wrote: >> > DTS team, >> > >> > I am making changes to DTS to support i217, i218 chipsets to DTS and I >> have >> > couple of questions >> > >> > 1. Any README on system pre-requisites? Can I run DTS natively on DUT >> > without any SSH? >> >> As I know currently not, but any patches are welcome :) >> Do you guys wants to use it in test env? >> > > I want to use it for development testing. > >> >> I know that it would be helpful in development, but for testing, it >> would be have a remote access to DUT. >> >> > I have I217 and 82540EM NICs in a system running Ubuntu. I would like >> to >> > use both NIC's for testing. If I use regular method of SSH, I will loose >> > one NIC hence the question. >> >> As I said, it only happens in develop mode, while for automation >> testing, it would be unacceptable to have no other NIC for control patch. >> >> Or it would be reasonable to add one serial port to control it in >> testing mode. >> >> > >> > 2. When I run DTS, for some of the commands I am getting garbage output. >> > The problem is seen on 2 Ubuntu systems. When I run those commands >> manually >> > commands work fine for e.g. >> >> I have a patch send out maybe can solve this, but I have not checked yet >> > > I will test the patch and let you know. > >> >> > *16/01/2015 12:58:00 DTS_TESTER_CMD: ls >> > /sys/bus/pci/devices/0000:00:19.0/net* >> > >> > *16/01/2015 12:58:00 DTS_TESTER_OUTPUT: ^[[0m^[[01;34meth0^[[0m* >> > >> > *16/01/2015 12:58:00 DTS_TESTER_CMD: Tester: [000:00:19.0 >> 8086:15a1] >> > ^[[0m^[[01;34meth0^[[0m* >> > >> > *16/01/2015 12:58:00 DTS_TESTER_CMD: cat >> > /sys/bus/pci/devices/0000:00:19.0/net/^[[0m^[[01;34meth0^[[0m/address* >> > >> > *16/01/2015 12:58:00 DTS_TESTER_OUTPUT: cat: >> > /sys/bus/pci/devices/0000:00:19.0/net/m1: No such file or directory^M* >> > >> > *-bash: 34meth0m/address: No such file or directory* >> > >> > *16/01/2015 12:58:00 DTS_TESTER_CMD: ls >> > /sys/bus/pci/devices/0000:04:02.0/net* >> > >> > *16/01/2015 12:58:00 DTS_TESTER_OUTPUT: ^[[0m^[[01;34meth1^[[0m* >> > >> > *16/01/2015 12:58:00 DTS_TESTER_CMD: Tester: [000:04:02.0 >> 8086:100e] >> > ^[[0m^[[01;34meth1^[[0m* >> > >> > *16/01/2015 12:58:00 DTS_TESTER_CMD: cat >> > /sys/bus/pci/devices/0000:04:02.0/net/^[[0m^[[01;34meth1^[[0m/address* >> > >> > >> > 3. Tests start failing with following msgs even though I217 NIC is >> > recognized. >> > >> > *Traceback (most recent call last):* >> > >> > * File "/home/rkerur/dpdk-dts/dts/framework/dts.py", line 527, in >> > execute_test_setup_all* >> > >> > * test_case.set_up_all()* >> > >> > * File "../tests/TestSuite_whitelist.py", line 61, in set_up_all* >> > >> > * self.verify(len(self.dutPorts) >= 1, "Insufficient ports")* >> > >> > * File "/home/rkerur/dpdk-dts/dts/framework/test_case.py", line 62, in >> > verify* >> >> This failure maybe because you only have one NIC port :), but two needs. >> > > Issue was primarily with delay to acquire v6 address after link up. > There are some test cases in DTS for 1 port and I am testing with them > right now. > > Thanks, > Ravi > >> >> Thanks, >> Michael >> > * raise VerifyFailure(description)* >> > >> > *VerifyFailure: 'Insufficient ports'* >> > >> > >> > >> > *16/01/2015 12:58:23 INFO:* >> > >> > *TEST SUITE ENDED: TestWhitelist* >> > >> > >> > Thanks, >> > >> > Ravi >> > >> >> >