From: Ravi Kerur <rkerur@gmail.com>
To: "Qiu, Michael" <michael.qiu@intel.com>, "Liu, Yong" <yong.liu@intel.com>
Cc: "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] Clarifications on setting up DUT
Date: Thu, 22 Jan 2015 08:43:18 -0800 [thread overview]
Message-ID: <CAFb4SLBVO7oGzxxpb1zTQSViRf610NnT2StbccbuW5osRfd5=A@mail.gmail.com> (raw)
In-Reply-To: <CAFb4SLBpcoH3dsan1vbSOHs_1f4e7sMzHRDAJTMDn0PRxyqqUw@mail.gmail.com>
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 <rkerur@gmail.com> 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 <rk>
>
> On Sun, Jan 18, 2015 at 5:19 PM, Qiu, Michael <michael.qiu@intel.com>
> 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?
>>
>
> <rk> 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
>>
>
> <rk> 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.
>>
>
> <rk> 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
>> >
>>
>>
>
next prev parent reply other threads:[~2015-01-22 16:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 21:09 Ravi Kerur
2015-01-19 1:19 ` Qiu, Michael
2015-01-19 19:07 ` Ravi Kerur
2015-01-22 16:43 ` Ravi Kerur [this message]
2015-01-19 12:43 Liu, Yong
2015-01-19 15:17 ` Thomas Monjalon
2015-01-19 18:00 ` Ravi Kerur
2015-01-23 14:18 ` Liu, Yong
2015-01-24 0:58 ` Ravi Kerur
2015-01-25 0:45 ` Liu, Yong
2015-01-26 21:20 ` Ravi Kerur
2015-01-27 3:23 ` Qiu, Michael
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='CAFb4SLBVO7oGzxxpb1zTQSViRf610NnT2StbccbuW5osRfd5=A@mail.gmail.com' \
--to=rkerur@gmail.com \
--cc=dts@dpdk.org \
--cc=michael.qiu@intel.com \
--cc=yong.liu@intel.com \
/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).