From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f53.google.com (mail-wm0-f53.google.com [74.125.82.53]) by dpdk.org (Postfix) with ESMTP id 4D6202BB9 for ; Thu, 8 Jun 2017 11:29:20 +0200 (CEST) Received: by mail-wm0-f53.google.com with SMTP id n195so26948395wmg.1 for ; Thu, 08 Jun 2017 02:29:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:subject:message-id:mime-version :content-transfer-encoding; bh=GY5aGsu9s9Kdm9+F1og3BZPFhdbha5kRIWoaCrsTXVs=; b=CwAg5b3BIV2ISpX0HvxDuC5csrdD9YH8XX8RACj7K5RbOInPTqB59Y72wE/IlHCvI6 SJnlAucKewP17AWC26Lk/aDCyvcrWrUEHQItOk3PxrrJfgxKGCdIY/gfqb+pBXc/E+mk LIgNUk6lB6QmwIL/pErAaTLMUaygGP2ZG+T0VPZG4V64318imU9ha1TMm2Mb5gYKm/rb ZawdcZ2N2ZBVHn21BlPtmPcClylKomIKRzINRVwzZ3nqfK2VMyYIkMdJF4JnDd1j/OF5 RV7MhL86/SiQtz8MpZfdhKlOy6qkn/atWK3Sc+r7b67Nm/GpFyhq8kvI8fXQgWj9VYti Oe2g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-transfer-encoding; bh=GY5aGsu9s9Kdm9+F1og3BZPFhdbha5kRIWoaCrsTXVs=; b=h2y+4+SI4X/2ixnlL8w4SWfMkHe7GQyn8jvMWFgU9XlyPOBJ0Ui12PFSTnMg9QjStE /A3z3FsHits8lTEXpPT/3ewyQf7kXLTHGJbPAtNgLD5iQvYoCfUho3Yt8dYcIpKWcXAu UESNI0UM7r41TTJK/uCN8rcywiHDyl6jJIBwmW1iVo4XE22LpOa0dXt/mBSADRHizY5m /Hua6sYQUX2Ap+1j4SyY3kW+lYyqI6/MBhOKndynvQb5xeGZ/b4scUECn7lE9NW3F0ov /qblArJqptDfI9Jb799OivQcuQbwZvSct7309N+FFhK9Ra0Ht9hHFQPij5m7HgNacrgt yG+Q== X-Gm-Message-State: AODbwcB+I5CodP7MR9glP1kcwmD+GJaqdBKEoK4Rm/MlbPn7yWDYgt++ pV0tRdS0mlbNWi6wQuY= X-Received: by 10.28.62.199 with SMTP id l190mr2828744wma.13.1496914159926; Thu, 08 Jun 2017 02:29:19 -0700 (PDT) Received: from platinum (2a01cb0c03c651000226b0fffeed02fc.ipv6.abo.wanadoo.fr. [2a01:cb0c:3c6:5100:226:b0ff:feed:2fc]) by smtp.gmail.com with ESMTPSA id x133sm5208207wme.0.2017.06.08.02.29.19 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 08 Jun 2017 02:29:19 -0700 (PDT) Date: Thu, 8 Jun 2017 11:29:17 +0200 From: Olivier Matz To: helin.zhang@intel.com, jingjing.wu@intel.com, dev@dpdk.org Message-ID: <20170608112917.22fb51eb@platinum> X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: [dpdk-dev] i40e: pci probe fails when using one bogus sfp 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: , X-List-Received-Date: Thu, 08 Jun 2017 09:29:20 -0000 Hi, One of our customers encounters an issue with dpdk when there is a bogus SFP on one of the ports. The following message is reported: PMD: eth_i40e_dev_init(): Failed to sync phy type: -95 (note: 95 is EOPNOTSUPP/ENOTSUP) Unfortunately I cannot reproduce the issue to give more details, but the hypothesis is that it fails in i40e_dev_sync_phy_type(). It could be related to that patch: http://dpdk.org/browse/dpdk/commit/?id=edfb226f69bf To me, the expected behavior should be: - pci probe is succesful - the initialization of the port with faulty SFP fails - the initialization of the other ports is succesful Do you have any comment or idea to fix this issue? Thanks, Olivier