From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 233F3A04B6; Thu, 17 Sep 2020 08:57:40 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 3DB9D1D553; Thu, 17 Sep 2020 08:57:39 +0200 (CEST) Received: from NAM11-DM6-obe.outbound.protection.outlook.com (mail-dm6nam11on2125.outbound.protection.outlook.com [40.107.223.125]) by dpdk.org (Postfix) with ESMTP id 4EEE61D54E for ; Thu, 17 Sep 2020 08:57:37 +0200 (CEST) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=bwPPw/HydZFp7fytv5Z+7dP0qHg+IQA0KHfHxW1lnTGdvced962eCglIbHpIPti7CugUlgQb35MRYCExENuGuxMTFVaCICru0Uafxx+z7WM2To2RrbY6kMqE1FluYyMoUNIoZ199azJK+zQOAyCBOf2yeVY7SUbAMIicvr0nThEjPLhBqKEdSGoDXL5VeS/LY8FR2e06NVx3TMboLJFTTT8DDl8/hhZYTbUUiN4aLdSwtC3UfgQOWkWxdsO23TEnp1qpN1LfjLlzxqbKJN0/rg1FE4iV20hcBETSiosBwq6JmbX2VihbRz6X1NXQPnw6Fh8xOpKZo1Q8Lpny/vpVaw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=MPX1uLUIkHMDXTMcNXUBSjoT3emaCt7qE9EwHVyFqBk=; b=G5lf+H4xxhiMD8+k/jOEFfqCF4g0pddRNd52zYTRAKctkFgRwOMbvhvh1dGrcvWorlttTnAqJCHt4s93JGTFZ0Yiw202UbNx6Vw6qTu6Z9UGaBmua1AxI/E0/orB18quM9/N/C1K1ETM1h0VySXBMbEjY/YBrTvKuegoAfEMJ4U3zAgaT270PXt9yYUV8717qTNUQT3OzqS95Ny/wGoww3ePG9FWB9quH/xghm8jLcW4hZMzjzRD2la2fN0UkF4DXCmtHIzKtDMfV5GFLg1y9Q7Z1lkyzDdy25rYkMNx7MJgsToM1zYHnLdEYhUJhZFRd6REDFlRuJk3Dh72wk5YZA== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=microsoft.com; dmarc=pass action=none header.from=microsoft.com; dkim=pass header.d=microsoft.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=MPX1uLUIkHMDXTMcNXUBSjoT3emaCt7qE9EwHVyFqBk=; b=CZzZ5/PYVqpXe0OtAfQnz6V/siyqUlRt0zp1g4aJHnvvPRy+6yPQly+AdYmkdv+X4kHLWtMpFEDzewP+IlyRXn0CxqnX2l4/4+WqoToj3sUa6OMB5D4DkRbP77y0itLXK/1SGzcgdOKkIT049+37HfvFvNs2PD4We+p7FpYbwo8= Received: from BN8PR21MB1155.namprd21.prod.outlook.com (2603:10b6:408:73::10) by BN6PR21MB0146.namprd21.prod.outlook.com (2603:10b6:404:93::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3412.1; Thu, 17 Sep 2020 06:57:34 +0000 Received: from BN8PR21MB1155.namprd21.prod.outlook.com ([fe80::4936:76bb:2ef7:e2e8]) by BN8PR21MB1155.namprd21.prod.outlook.com ([fe80::4936:76bb:2ef7:e2e8%5]) with mapi id 15.20.3412.004; Thu, 17 Sep 2020 06:57:34 +0000 From: Long Li To: "Dey, Souvik" , Kevin Traynor , "dev@dpdk.org" CC: Stephen Hemminger , "Yigit, Ferruh" , Stephen Hemminger Thread-Topic: [dpdk-dev] Issue with net/netvsc pmd in 18.11.9 Thread-Index: AdaMHsW3cCwXsyP/Rn6fVvBLPu8+lwAFXQWAAACyOIAABkS5YAAELNogAAHddhAAA0nSEAASYq0C Date: Thu, 17 Sep 2020 06:57:34 +0000 Message-ID: References: <82871b97-8145-d3e4-a87f-28aa61cc8e61@redhat.com> , In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=True; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2020-09-17T06:57:33.835Z; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=General; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ContentBits=0; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Method=Standard; authentication-results: rbbn.com; dkim=none (message not signed) header.d=none;rbbn.com; dmarc=none action=none header.from=microsoft.com; x-originating-ip: [67.168.111.68] x-ms-publictraffictype: Email x-ms-office365-filtering-ht: Tenant x-ms-office365-filtering-correlation-id: 46194e30-994b-4bec-9ece-08d85ad6f4b6 x-ms-traffictypediagnostic: BN6PR21MB0146: x-ms-exchange-transport-forked: True x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:10000; x-ms-exchange-senderadcheck: 1 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: WHPv/m8GXn9iCVQ1i/S32IdbrlPTb3Y51UPQYpYqsBbSZC4NkLs7kwCvq0KhAmIWE684qXTIJZzloFkA0taR1+r7EMs7XB+x+3yYeAouAcq15GfjLRCJl/qW4e8ZtZsirxXHpyB5BOh9u6QE6H8utYYeezmGaXy2aixM9y/5BOoNMSa5AeksR4srL5xvpFpktW2dWvaeuqD51oxIIeZ97jcFVxVAwYuLayIOmrAifHKympqVODD4LXiMY5VVkZAxEnZkk9wyOltgM9SSyKbSGQ9AwdKNQRDsEgqhF4fOzLOjxfDgplZNxIzGWQZkTCtskvZ3I/f0niKsSzpGpT9II9jlVEIJsy8fvhSNgjvtG3oZ30ceSyDQPC3h9CqOxg4bYJldvkglk392Pq1ySv9CVSFSBFhFxnV4IPJROlCFgZYr1YcDjgVr9ijS+p8LAavTm/UeWr19pnbZs6rORk4yug== x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BN8PR21MB1155.namprd21.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(39860400002)(396003)(376002)(346002)(366004)(136003)(7696005)(5660300002)(8676002)(316002)(110136005)(66476007)(54906003)(478600001)(66446008)(66556008)(76116006)(64756008)(8936002)(10290500003)(66946007)(86362001)(107886003)(9686003)(186003)(6506007)(26005)(166002)(30864003)(4326008)(83380400001)(82950400001)(82960400001)(52536014)(55016002)(33656002)(2906002)(966005)(8990500004)(53546011)(19627405001)(71200400001); DIR:OUT; SFP:1102; x-ms-exchange-antispam-messagedata: smdS/7+pqLutn4igfKAvw0eirFPwwQp5XR5QBj7C2eiokSGxcrWo02eLjrJNssLUHWiSEhx4aXuidd+/2VUHg1oMT4FQcki1P9BSJLidZUxa8872dMhoK9EJoKxItr5w9TppnFZVpFNovcFbmh2wCZy5Erkp2BDQJNU1hpA9qBp0uGj+cOAzRuQXWk10pGM5qVTCS/LOcV/GFzzwpY+sdRe8KEud911I+KBGeDQMcG4ScD7nv/x82wuIxcO6f7U0cW0UBTxDPxcVP9CzkL+DQ2Q1V3Mzx9RSs2cRfLmf3MO46bUFtAXEHkTMv4QOauEcjPypOQ4tHCHlVSk7TBNjw7NLGshrbmCcIj+1jmXmHXvbw4U/KFGwZX9ZyXBytfwLErFf7T5ocHn8m/OY/02S3zVwlb2p81RAOi0buF48UNtZJG9Y+3HJY7UboFzZYssqShH5FprVBdfHFuBzT5Qhfas9Rw6+woZVmv6zs3YjOCmM9vSf5kvf6L0maQ5Y8jNsLZ7w6I78xuHSniIvT8xeAUG/Ce6vxd5xbUBhOdK5CVPLNzITROb2DRQc8wLOHDq9JfDJ0a+7K1rfXQ/zA9cZwBwQ9nDuAJYY9NixqYJExynsf4jKZiQcmIWZ5Y7/pY2SIo8PRZrk+fzH1QP0kiQMDg== MIME-Version: 1.0 X-OriginatorOrg: microsoft.com X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: BN8PR21MB1155.namprd21.prod.outlook.com X-MS-Exchange-CrossTenant-Network-Message-Id: 46194e30-994b-4bec-9ece-08d85ad6f4b6 X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Sep 2020 06:57:34.6666 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47 X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: AobP4pn9pLB7I6JME6WR7e9z26RHWrGXu6o7F00N0+kGbJ6VhV8wJ90w/nCIG7WDJG0aUeEHRa3mSTPRJc7gVw== X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR21MB0146 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] Issue with net/netvsc pmd in 18.11.9 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" The patch below is correct. I'm wondering if you have missed another patch.= The most suspects are "77cf88c0c6 net/netvsc: fix underflow when Rx extern= al mbuf" and https://patches.dpdk.org/patch/67511/. Can yo= u confirm you have those? Do you have the log from "--log-level pmd.netvsc:debug" on the new failure? Also, it seems you are running with "-vdev=3Dnet_vdev_netvsc0,iface=3Dmlxhv= pkt0 --vdev=3Dnet_vdev_netvsc1,iface=3Dmlxhvpkt1", I'm not entirely sure ho= w netvsc pmd is involved. Can you provide some details on your setup? I'll try to repro it to see if = I can hit the failure. ________________________________ From: Dey, Souvik Sent: Wednesday, September 16, 2020 3:07 PM To: Long Li ; Kevin Traynor ; de= v@dpdk.org Cc: Stephen Hemminger ; Yigit, Ferruh ; Stephen Hemminger Subject: RE: [dpdk-dev] Issue with net/netvsc pmd in 18.11.9 Looks like the below patch has changes a lot in the tx path which came in 1= 8.11.9. Verified till 18.11.8 everything is working as expected. https://patches.dpdk.org/patch/67511/ Can you confirm if this change or the recv change patch proposed below will= require any specific device config change as my same app does not work any= longer. -- Regards, Souvik From: Dey, Souvik Sent: Wednesday, September 16, 2020 4:32 PM To: Long Li ; Kevin Traynor ; de= v@dpdk.org Cc: Stephen Hemminger ; Yigit, Ferruh ; Stephen Hemminger Subject: RE: [dpdk-dev] Issue with net/netvsc pmd in 18.11.9 If it helps the tx_conf->tx_free_thresh is set to 0 from app side and nb_de= sc is set to 4096 from the app. The same was set in 18.11.6 too. From: Dey, Souvik Sent: Wednesday, September 16, 2020 3:44 PM To: 'Long Li' >; Kevin Tr= aynor >; dev@dpdk.org Cc: Stephen Hemminger >; Yigit, Ferruh >; Stephen Hemminger > Subject: RE: [dpdk-dev] Issue with net/netvsc pmd in 18.11.9 Hi Long, I did take this patch on top of 18.11.10rc1 , but with this patch and also = with 18.11.10rc1 files, the rx itself is not working and dhcp fails. With 1= 8.11.9 the rx is working fine and changes present in 18.11.10rc1(hn_rxtx.c = ) does not look to work. 18.11.6 was all proper but 18.11.9 is not helping= . I am not using testpmd but using our own dpdk app on Azure. We are using the below command line args: -c 0xe -n 3 -w 83f0:00:02.0 -w 8cb0:00:02.0 --vdev=3Dnet_vdev_netvsc0,iface= =3Dmlxhvpkt0 --vdev=3Dnet_vdev_netvsc1,iface=3Dmlxhvpkt1 --log-level pmd.ne= tvsc:debug --proc-type=3Dprimary Thanks in advance for all the help. -- Regards, Souvik From: Long Li > Sent: Wednesday, September 16, 2020 1:44 PM To: Dey, Souvik >; Kevin Traynor >; dev@dpdk.org Cc: Stephen Hemminger >; Yigit, Ferruh >; Stephen Hemminger > Subject: RE: [dpdk-dev] Issue with net/netvsc pmd in 18.11.9 ________________________________ NOTICE: This email was received from an EXTERNAL sender ________________________________ Hi Souvik, Please also pick up this patch: https://patchwork.dpdk.org/patch/75341/ This patch didn=92t make it to 18.11. Let me know if you are still seeing failures. If you can reproduce the fail= ure with testpmd or other tools in DPDK, please also share the command you = used. Thanks, Long From: Dey, Souvik > Sent: Wednesday, September 16, 2020 7:41 AM To: Kevin Traynor >; dev@dp= dk.org Cc: Stephen Hemminger >; Long Li >; Yi= git, Ferruh >; Stephe= n Hemminger > Subject: RE: [dpdk-dev] Issue with net/netvsc pmd in 18.11.9 Yes the patch solves the seg fault issue, but even after backporting the pa= tch we are not able to send packets with size higher than 512. The packets = not being transmitted is the real problem here. I have also tried to take t= he 18.11.10rc1 build but faced similar issues in transmitting the packets. -- Regards, Souvik From: dev > On Behalf Of = Kevin Traynor Sent: Wednesday, September 16, 2020 10:18 AM To: Dey, Souvik >; dev@dpdk.org Cc: Stephen Hemminger >; longli@microsoft.com; Yigit, Ferru= h >; sthemmin@microso= ft.com Subject: Re: [dpdk-dev] Issue with net/netvsc pmd in 18.11.9 ________________________________ NOTICE: This email was received from an EXTERNAL sender ________________________________ On 16/09/2020 13:00, Dey, Souvik wrote: > Hi All, > I updated from dpdk 18.11.6 to 18.11.9 and my netvsc pmd stopped working = as expected. Firstly, I saw a crash in tx packets as soon as the dpdk app c= omes up. In doing some googling found a bug that was fixed after 18.11.9 ht= tps://patches.dpdk.org/patch/75001/ . Ported this fix and was = able to get rid of the seg fault, but now stuck at another issue. When we a= re transmitting packets of size within HN_TXCOPY_THRESHOLD we Hi, The patch mentioned is merged to the 18.11 branch in dpdk-stable repo and part of 18.11.10-rc1, so expected to be in 18.11.10. ETA 28th September= . In case it's already fixed, you can try the 18.11.10-rc1 release. These netvsc backports were added since 18.11.9. The corresponding dpdk main commit id's are in the full log. $ git log --oneline v18.11.9..HEAD . 363bdf0f49 net/netvsc: fix chimney index 5b3a327709 net/netvsc: fix crash during Tx 77cf88c0c6 net/netvsc: fix underflow when Rx external mbuf 59257aaaa1 net/netvsc: do not spin forever waiting for reply The list of fixes that were tagged for stable but not backported is here: http://inbox.dpdk.org/stable/20200901100115.72365-1-ktraynor@redhat.com/ are all good but any larger packets/fragmented packets are getting dropped after some time. As soon as we start to receive the transmit completion event NVS_TYPE_RNDIS_ACK as failed, packets with size greater than HN_TXCOPY_THRESHOLD starts to drop and never recovers. Packets less than HN_TXCOPY_THRESHOLD works properly there after though. Any idea why this is happening and is there is some fix which is already there which is done after 18.11.9 release ? Maybe you can bisect the 18.11 branch to find where it stops working, there is only ~10 netvsc commits between 18.11.6 and 18.11.9. The release notes [1] or git history will tell you which commits are in which releases. Bear in mind that some commits were rebased for 18.11, so if you find the offending commit, you might want to check that it was correctly backported too. Kevin. [1] http://doc.dpdk.org/guides-18.11/rel_notes/release_18_11.html > We are at the critical part of our release, so any help in this regard wi= ll be highly appreciated. Thanks in advance for all the help. > > PS: I also tried to put the net/netvsc: return the correct chimney index = > fix in but nothing changed= . > > -- > Regards, > Souvik > > Log Snippet: > I can see the below errors coming after some transmitting. > hn_xmit_sg() tx: port 2:0 tx 4294967295 segs 2 size 0 > hn_xmit_sg() tx: port 2:0 tx 4294967295 segs 3 size 0 > hn_xmit_sg() tx: port 2:0 tx 4294967295 segs 2 size 0 > hn_xmit_sg() tx: port 2:0 tx 4294967295 segs 3 size 0 > hn_xmit_sg() tx: port 2:0 tx 4294967295 segs 2 size 0 > hn_xmit_sg() tx: port 2:0 tx 4294967295 segs 3 size 0 > hn_xmit_sg() tx: port 2:0 tx 4294967295 segs 2 size 0 > hn_xmit_sg() tx: port 2:0 tx 4294967295 segs 3 size 0 > hn_xmit_sg() tx: port 2:0 tx 4294967295 segs 2 size 0 > hn_xmit_sg() tx: port 2:0 tx 4294967295 segs 3 size 0 > hn_flush_txagg() tx: port 2:0 tx 2048 size 302 > hn_nvs_send_completed() tx: port 2:0 complete tx 4294967295 packets 1 byt= es 1514 > hn_nvs_send_completed() tx: port 2:0 complete tx 4294967295 packets 1 byt= es 1514 > hn_nvs_send_completed() tx: port 2:0 complete tx 4294967295 packets 1 byt= es 1514 > hn_nvs_send_completed() tx: port 2:0 complete tx 4294967295 packets 1 byt= es 1514 > hn_nvs_send_completed() tx: port 2:0 complete tx 4294967295 packets 1 byt= es 1514 > hn_nvs_send_completed() tx: port 2:0 complete tx 4294967295 packets 1 byt= es 1514 > hn_nvs_send_completed() tx: port 2:0 complete tx 4294967295 packets 1 byt= es 1514 > hn_nvs_send_completed() tx: port 2:0 complete tx 4294967295 packets 1 byt= es 1514 > hn_nvs_send_completed() tx: port 2:0 complete tx 4294967295 packets 1 byt= es 1514 > hn_nvs_send_completed() tx: port 2:0 complete tx 4294967295 packets 1 byt= es 1514 > hn_nvs_send_completed() tx: port 2:0 complete tx 2048 packets 1 bytes 242 > > hn_xmit_sg() tx: port 2:0 tx 4294967295 segs 2 size 0 > hn_xmit_sg() tx: port 2:0 tx 4294967295 segs 2 size 0 > hn_xmit_sg() tx: port 2:0 tx 4294967295 segs 2 size 0 > hn_xmit_sg() tx: port 2:0 tx 4294967295 segs 3 size 0 > hn_xmit_sg() tx: port 2:0 tx 4294967295 segs 2 size 0 > hn_xmit_sg() tx: port 2:0 tx 4294967295 segs 3 size 0 > hn_xmit_sg() tx: port 2:0 tx 4294967295 segs 2 size 0 > hn_xmit_sg() tx: port 2:0 tx 4294967295 segs 2 size 0 > hn_xmit_sg() tx: port 2:0 tx 4294967295 segs 3 size 0 > hn_xmit_sg() tx: port 2:0 tx 4294967295 segs 2 size 0 > hn_flush_txagg() tx: port 2:0 tx 2624 size 302 > hn_nvs_send_completed() tx: port 2:0 complete tx 4294967295 failed status= 2 > hn_nvs_send_completed() tx: port 2:0 complete tx 4294967295 failed status= 2 > hn_nvs_send_completed() tx: port 2:0 complete tx 4294967295 failed status= 2 > hn_nvs_send_completed() tx: port 2:0 complete tx 4294967295 failed status= 2 > hn_nvs_send_completed() tx: port 2:0 complete tx 4294967295 packets 1 byt= es 1514 > hn_nvs_send_completed() tx: port 2:0 complete tx 4294967295 packets 1 byt= es 1514 > hn_nvs_send_completed() tx: port 2:0 complete tx 4294967295 packets 1 byt= es 1514 > hn_nvs_send_completed() tx: port 2:0 complete tx 4294967295 packets 1 byt= es 1514 > hn_nvs_send_completed() tx: port 2:0 complete tx 4294967295 packets 1 byt= es 1514 > hn_nvs_send_completed() tx: port 2:0 complete tx 4294967295 packets 1 byt= es 1514 > hn_nvs_send_completed() tx: port 2:0 complete tx 2624 packets 1 bytes 242 > > hn_xmit_sg() tx: port 2:0 tx 4294967295 segs 2 size 0 > hn_xmit_sg() tx: port 2:0 tx 4294967295 segs 2 size 0 > hn_xmit_sg() tx: port 2:0 tx 4294967295 segs 2 size 0 > hn_xmit_sg() tx: port 2:0 tx 4294967295 segs 3 size 0 > hn_xmit_sg() tx: port 2:0 tx 4294967295 segs 2 size 0 > hn_xmit_sg() tx: port 2:0 tx 4294967295 segs 3 size 0 > hn_xmit_sg() tx: port 2:0 tx 4294967295 segs 2 size 0 > hn_xmit_sg() tx: port 2:0 tx 4294967295 segs 2 size 0 > hn_xmit_sg() tx: port 2:0 tx 4294967295 segs 3 size 0 > hn_xmit_sg() tx: port 2:0 tx 4294967295 segs 2 size 0 > hn_flush_txagg() tx: port 2:0 tx 2688 size 302 > hn_nvs_send_completed() tx: port 2:0 complete tx 4294967295 failed status= 2 > hn_nvs_send_completed() tx: port 2:0 complete tx 4294967295 failed status= 2 > hn_nvs_send_completed() tx: port 2:0 complete tx 4294967295 failed status= 2 > hn_nvs_send_completed() tx: port 2:0 complete tx 4294967295 failed status= 2 > hn_nvs_send_completed() tx: port 2:0 complete tx 4294967295 failed status= 2 > hn_nvs_send_completed() tx: port 2:0 complete tx 4294967295 failed status= 2 > hn_nvs_send_completed() tx: port 2:0 complete tx 4294967295 failed status= 2 > hn_nvs_send_completed() tx: port 2:0 complete tx 4294967295 failed status= 2 > hn_nvs_send_completed() tx: port 2:0 complete tx 4294967295 failed status= 2 > hn_nvs_send_completed() tx: port 2:0 complete tx 4294967295 failed status= 2 > hn_nvs_send_completed() tx: port 2:0 complete tx 2688 packets 1 bytes 242 > hn_flush_txagg() tx: port 2:0 tx 3264 size 571 > hn_nvs_send_completed() tx: port 2:0 complete tx 3264 packets 1 bytes 511 > hn_rxpkt() rx: port 2:0 RX id 3 size 511 type 0x11 ol_flags 0x2 > hn_flush_txagg() tx: port 2:0 tx 3328 size 571 > hn_nvs_send_completed() tx: port 2:0 complete tx 3328 packets 1 bytes 511 > hn_rxpkt() rx: port 2:0 RX id 3 size 512 type 0x11 ol_flags 0x2 > hn_xmit_sg() tx: port 2:0 tx 4294967295 segs 2 size 0 > hn_nvs_send_completed() tx: port 2:0 complete tx 4294967295 failed status= 2 > hn_rxpkt() rx: port 2:0 RX id 3 size 512 type 0x11 ol_flags 0x2 > hn_xmit_sg() tx: port 2:0 tx 4294967295 segs 2 size 0 > hn_nvs_send_completed() tx: port 2:0 complete tx 4294967295 failed status= 2 > hn_flush_txagg() tx: port 2:0 tx 3392 size 120 > hn_nvs_send_completed() tx: port 2:0 complete tx 3392 packets 1 bytes 60 > hn_rxpkt() rx: port 2:0 RX id 3 size 42 type 0x1 ol_flags 0 > ________________________________ Notice: This e-mail together with any attachments may contain information o= f Ribbon Communications Inc. that is confidential and/or proprietary for th= e sole use of the intended recipient. Any review, disclosure, reliance or d= istribution by others or forwarding without express permission is strictly = prohibited. If you are not the intended recipient, please notify the sender= immediately and then delete all copies, including any attachments. ________________________________