From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id DA079A034F for ; Tue, 23 Mar 2021 00:50:48 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 59D784014D; Tue, 23 Mar 2021 00:50:48 +0100 (CET) Received: from smtp.fortinet.com (smtp.fortinet.com [208.91.113.81]) by mails.dpdk.org (Postfix) with ESMTP id B129540143 for ; Tue, 23 Mar 2021 00:50:46 +0100 (CET) Received: from mail.fortinet.com ([192.168.221.133]) by smtp.fortinet.com with ESMTP id 12MNoiv7005266-12MNoiv9005266 (version=TLSv1.2 cipher=AES256-SHA256 bits=256 verify=FAIL) for ; Mon, 22 Mar 2021 16:50:44 -0700 Received: from FGT-EXCH-MBX132.fortinet-us.com (192.168.221.132) by FGT-EXCH-MBX133.fortinet-us.com (192.168.221.133) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Mon, 22 Mar 2021 16:50:44 -0700 Received: from FGT-EXCH-MBX132.fortinet-us.com ([fe80::78b9:5f97:8cec:b419]) by FGT-EXCH-MBX132.fortinet-us.com ([fe80::78b9:5f97:8cec:b419%8]) with mapi id 15.01.2176.009; Mon, 22 Mar 2021 16:50:43 -0700 From: Liwu Liu To: "users@dpdk.org" Thread-Topic: Intel E810C net_iavf PMD triggers MDD for second life. Thread-Index: Adcfdh3A/h1mPXr8Q/2MmGE3eDZ20g== Date: Mon, 22 Mar 2021 23:50:43 +0000 Message-ID: <44be676f551b4a41888adb39cbeb0dd9@fortinet.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [96.45.36.15] MIME-Version: 1.0 X-FE-Policy-ID-smtp.fortinet.com: 392:1:4:SYSTEM DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=fortinet.com; s=dkim; c=relaxed/relaxed; h=from:to:subject:date:message-id:content-type:mime-version; bh=OzmIy/h1DuK+OdMiff5Joz16UnNkpPLf4/bMLvIybi4=; b=aeOFyUnBRwn6KLrWfdSPt/dLaeJ+Q432+CS3LU9gbUgfzQTMDB+I6nNKAIl5rSWfb9/pCesCR1wU YeaBNbps0Zpz2U3QXKoPVOOqj2HSO0JOFAfZYHNZleKSBXs/nP+OtCRTD5h/TJIj0WRNglG5LnwM YRgSx1QTpFdBZ49y2zv1B8GbIAH9ziUhx8hBRWXZJd2an7oTVdyxt9NivMG0WmIP4k0OhNa+dHAs sEBN1i57e05IYxVKdq3mdEkDRPXMSuiRMrabsGsCQp690S+d3mX2Unq/C5tmIWWwO7EykPDf/VER xJQu1Oa87i1wrC6NmwrclE2fO+BYJ78iOJHHrA== Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: [dpdk-users] Intel E810C net_iavf PMD triggers MDD for second life. X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org Sender: "users" Hi Team, I am using DPDK 19.11 net_iavf under Linux 4.19 guest to drive vfNIC of I= ntel E810 cards. The host is ESXi 6.7. What I found out is that, if I start the PMD the second time, the host sh= all detect MDD (malicious device detection) status and the TXRX of the vf= NIC is disable. (The first life of PMD is working fine) Would prefer your hints/suggestions on how to work on this? Since upgradi= ng to 20.11 is kind of heavy for us, is there any specific incremental ch= anges based on 19.11 to walk around this? Many thanks for help, Sincerely Liwu ----Mode details----- [root@localhost:~] esxcli network nic get -n vmnic6 Advertised Auto Negotiation: true Advertised Link Modes: Auto, 25000BaseCR1/Full, 25000BaseSR/Full, 2500= 0BaseLR/Full, 50000BaseCR1/Full, 50000BaseSR/Full, 50000BaseLR/Full, 1000= 00BaseCR4/Full, 100000BaseSR4/Full, 100000BaseLR4/Full, 100000BaseCR1/Ful= l, 100000BaseSR/Full Auto Negotiation: true Cable Type: FIBRE Current Message Level: 0 Driver Info: Bus Info: 0000:3b:00:0 Driver: icen Firmware Version: 1.40 0x80003ab8 1.2735.0 Version: 1.4.2.0 Link Detected: true Link Status: Up Name: vmnic6 PHYAddress: 0 Pause Autonegotiate: false Pause RX: false Pause TX: false Supported Ports: FIBRE Supports Auto Negotiation: true Supports Pause: true Supports Wakeon: false Transceiver: Virtual Address: 00:50:56:54:5f:c3 Wakeon: None vmnic6 0000:3b:00.0 icen Up Up 100000 Full = 40:a6:b7:18:f9:e8 1500 Intel(R) Ethernet Controller E810-C for QSFP vmnic7 0000:3b:00.1 icen Up Up 100000 Full = 40:a6:b7:18:f9:e9 1500 Intel(R) Ethernet Controller E810-C for QSFP [root@localhost:~] esxcfg-module --get-options icen icen enabled =3D 1 options =3D 'NumQPsPerVF=3D16,16 max_vfs=3D4,4 ' 2021-03-22T23:41:14.556Z cpu0:2098179)WARNING: icen: indrv_DisableEnableQ= ueueMsg:1585: vqs->rx_queues is a NULL pointer! 2021-03-22T23:41:14.775Z cpu13:2098189)WARNING: icen: icen_ConfigureTxQue= ue:607: 0000:3b:00.1: Failed to set LAN Tx queue context for absolute Tx = queue 24, error ICE_ERR_PARAM 2021-03-22T23:41:14.775Z cpu13:2098189)WARNING: icen: indrv_SendMsgToVf:5= 55: 0000:3b:00.1: VF 1 failed opcode 6, error -5 2021-03-22T23:41:14.795Z cpu13:2098189)icen: indrv_CheckVfPermission:1695= : 0000:3b:00.1: 00:0c:29:70:fd:b9 already set for VF 1 2021-03-22T23:41:14.805Z cpu13:2098189)WARNING: icen: indrv_DisableEnable= QueueMsg:1585: vqs->rx_queues is a NULL pointer! 2021-03-22T23:41:14.815Z cpu13:2098189)WARNING: icen: indrv_DisableEnable= QueueMsg:1585: vqs->rx_queues is a NULL pointer! 2021-03-22T23:41:14.825Z cpu13:2098189)WARNING: icen: indrv_DisableEnable= QueueMsg:1585: vqs->rx_queues is a NULL pointer! 2021-03-22T23:41:14.835Z cpu13:2098189)WARNING: icen: indrv_DisableEnable= QueueMsg:1585: vqs->rx_queues is a NULL pointer! 2021-03-22T23:41:14.845Z cpu13:2098189)WARNING: icen: indrv_DisableEnable= QueueMsg:1585: vqs->rx_queues is a NULL pointer! 2021-03-22T23:41:14.855Z cpu13:2098189)WARNING: icen: indrv_DisableEnable= QueueMsg:1585: vqs->rx_queues is a NULL pointer! 2021-03-22T23:41:14.865Z cpu13:2098189)WARNING: icen: indrv_DisableEnable= QueueMsg:1585: vqs->rx_queues is a NULL pointer! 2021-03-22T23:41:14.875Z cpu13:2098189)WARNING: icen: indrv_DisableEnable= QueueMsg:1585: vqs->rx_queues is a NULL pointer! 2021-03-22T23:41:14.885Z cpu13:2098189)WARNING: icen: indrv_DisableEnable= QueueMsg:1585: vqs->rx_queues is a NULL pointer! 2021-03-22T23:41:14.895Z cpu13:2098189)WARNING: icen: indrv_DisableEnable= QueueMsg:1585: vqs->rx_queues is a NULL pointer! 2021-03-22T23:41:14.905Z cpu13:2098189)WARNING: icen: indrv_DisableEnable= QueueMsg:1585: vqs->rx_queues is a NULL pointer! 2021-03-22T23:41:14.915Z cpu13:2098189)WARNING: icen: indrv_DisableEnable= QueueMsg:1585: vqs->rx_queues is a NULL pointer! 2021-03-22T23:41:14.925Z cpu13:2098189)WARNING: icen: indrv_DisableEnable= QueueMsg:1585: vqs->rx_queues is a NULL pointer! 2021-03-22T23:41:14.935Z cpu13:2098189)WARNING: icen: indrv_DisableEnable= QueueMsg:1585: vqs->rx_queues is a NULL pointer! 2021-03-22T23:41:14.945Z cpu13:2098189)WARNING: icen: indrv_DisableEnable= QueueMsg:1585: vqs->rx_queues is a NULL pointer! 2021-03-22T23:41:14.955Z cpu13:2098189)WARNING: icen: indrv_DisableEnable= QueueMsg:1585: vqs->rx_queues is a NULL pointer! 2021-03-22T23:41:15.152Z cpu10:2098178)WARNING: icen: indrv_ReportMddSubt= ask:7034: 0000:3b:00.0: 0 Rx Malicious Driver Detection events detected o= n VF1, MAC: 00:0c:29:70:fd:b8 2021-03-22T23:41:15.152Z cpu10:2098178)WARNING: icen: indrv_ReportMddSubt= ask:7038: 0000:3b:00.0: 3 Tx Malicious Driver Detection events detected o= n VF1, MAC: 00:0c:29:70:fd:b8 2021-03-22T23:41:15.524Z cpu10:2098188)WARNING: icen: indrv_ReportMddSubt= ask:7034: 0000:3b:00.1: 0 Rx Malicious Driver Detection events detected o= n VF1, MAC: 00:0c:29:70:fd:b9 2021-03-22T23:41:15.524Z cpu10:2098188)WARNING: icen: indrv_ReportMddSubt= ask:7038: 0000:3b:00.1: 2 Tx Malicious Driver Detection events detected o= n VF1, MAC: 00:0c:29:70:fd:b9 *** Please note that this message and any attachments may contain confid= ential and proprietary material and information and are intended only for= the use of the intended recipient(s). If you are not the intended recipi= ent, you are hereby notified that any review, use, disclosure, disseminat= ion, distribution or copying of this message and any attachments is stric= tly prohibited. If you have received this email in error, please immediat= ely notify the sender and destroy this e-mail and any attachments and all= copies, whether electronic or printed. Please also note that any views, = opinions, conclusions or commitments expressed in this message are those = of the individual sender and do not necessarily reflect the views of Fort= inet, Inc., its affiliates, and emails are not binding on Fortinet and on= ly a writing manually signed by Fortinet's General Counsel can be a bindi= ng commitment of Fortinet to Fortinet's customers or partners. Thank you.= ***