Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp587320pxk; Thu, 24 Sep 2020 13:03:34 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwwMlu8vX1FMjYCXsW7/x82bJ3GZE0CtnKbBo8Nzm07XvTJQJJvZsBZjAMgPfFgY2H87YVJ X-Received: by 2002:a50:bb62:: with SMTP id y89mr457659ede.261.1600977814284; Thu, 24 Sep 2020 13:03:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1600977814; cv=none; d=google.com; s=arc-20160816; b=mwIbg9sN+SeaKN6j++gWAQP/IAmzfDBoG7Dor9dh+bqhRfhpcTuMyLGClC0gwmgp13 lTGTUATfrr0msxTubq2QQfhfljOkxgvDU+xJYmSvsN2KZvgiOOMcTbnyHiR2mqYb5c/T Ejny9V+QSCOnhtYSDDbjoZVXLuqrpkXI/R9mSXuAgEYk4mSjPzmC25DBmj8reN/CUB60 WtzilY5mrCVgZhaAVMX/VJDasbAZRm/BqvfIvY7Se4Us8Qmdu+hjZqR2vY+dyI7Qgg93 3rKggU5hhp64MqYlX2bnC29B0Yzrtn5DD6OIR0JfWVRLnb7AOsCKDRvY5/E78VAc7HL/ DPVQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=K8NsKF8ySQUWx+1FOFhsKxoRSfSCSSiIkAvjEMs007w=; b=o6yGUHQYgmlY52wl6ou/0TV0azdkE/SWF41dBofqyaU4d2R8XA4AsAxJsJc06aiRbf eUp6F9qRuHZAO+ObD3CSPFzlwmkpCjE19rtYqf17guFkh/RhuXXjTRltMkR5DmM/hmfE Dy0tOqBFZecsYcdKNKN3pYHrDgbEmAysTqc9ydHtpDyzztHtJsFYlSu76XmNejQXw1Ff Oj2JimxZwsxsG2vraZSHM03/kmoL50Zi8WGh1qIN4RY6GDdj75gKxLlM7a+L01DtvgFF e0kE/TChh2d7O0tcL0mF3x3Dd6orNuoMP4NFwRSeeQrHH9J5FJiwRw/ha+NQ1bTtI0Di Dh1A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id v16si468822ejk.553.2020.09.24.13.03.08; Thu, 24 Sep 2020 13:03:34 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726444AbgIXT5d (ORCPT + 99 others); Thu, 24 Sep 2020 15:57:33 -0400 Received: from vps0.lunn.ch ([185.16.172.187]:53748 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725208AbgIXT5d (ORCPT ); Thu, 24 Sep 2020 15:57:33 -0400 Received: from andrew by vps0.lunn.ch with local (Exim 4.94) (envelope-from ) id 1kLXMl-00G4IN-8C; Thu, 24 Sep 2020 21:57:19 +0200 Date: Thu, 24 Sep 2020 21:57:19 +0200 From: Andrew Lunn To: Kai-Heng Feng Cc: jeffrey.t.kirsher@intel.com, "David S. Miller" , Jakub Kicinski , "moderated list:INTEL ETHERNET DRIVERS" , "open list:NETWORKING DRIVERS" , open list Subject: Re: [PATCH v3] e1000e: Increase iteration on polling MDIC ready bit Message-ID: <20200924195719.GF3821492@lunn.ch> References: <20200924150958.18016-1-kai.heng.feng@canonical.com> <20200924164542.19906-1-kai.heng.feng@canonical.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200924164542.19906-1-kai.heng.feng@canonical.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Sep 25, 2020 at 12:45:42AM +0800, Kai-Heng Feng wrote: > We are seeing the following error after S3 resume: > [ 704.746874] e1000e 0000:00:1f.6 eno1: Setting page 0x6020 > [ 704.844232] e1000e 0000:00:1f.6 eno1: MDI Write did not complete > [ 704.902817] e1000e 0000:00:1f.6 eno1: Setting page 0x6020 > [ 704.903075] e1000e 0000:00:1f.6 eno1: reading PHY page 769 (or 0x6020 shifted) reg 0x17 > [ 704.903281] e1000e 0000:00:1f.6 eno1: Setting page 0x6020 > [ 704.903486] e1000e 0000:00:1f.6 eno1: writing PHY page 769 (or 0x6020 shifted) reg 0x17 > [ 704.943155] e1000e 0000:00:1f.6 eno1: MDI Error > ... > [ 705.108161] e1000e 0000:00:1f.6 eno1: Hardware Error > > As Andrew Lunn pointed out, MDIO has nothing to do with phy, and indeed > increase polling iteration can resolve the issue. > > The root cause is quite likely Intel ME, since it's a blackbox to the > kernel so the only approach we can take is to be patient and wait > longer. Please could you explain how you see Intel ME being responsible for this. I'm not convinced. Andrew