From: Andrew Lunn <andrew@lunn.ch>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH v3] e1000e: Increase iteration on polling MDIC ready bit
Date: Thu, 24 Sep 2020 21:57:19 +0200 [thread overview]
Message-ID: <20200924195719.GF3821492@lunn.ch> (raw)
In-Reply-To: <20200924164542.19906-1-kai.heng.feng@canonical.com>
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
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Lunn <andrew@lunn.ch>
To: Kai-Heng Feng <kai.heng.feng@canonical.com>
Cc: jeffrey.t.kirsher@intel.com,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
"moderated list:INTEL ETHERNET DRIVERS"
<intel-wired-lan@lists.osuosl.org>,
"open list:NETWORKING DRIVERS" <netdev@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] e1000e: Increase iteration on polling MDIC ready bit
Date: Thu, 24 Sep 2020 21:57:19 +0200 [thread overview]
Message-ID: <20200924195719.GF3821492@lunn.ch> (raw)
In-Reply-To: <20200924164542.19906-1-kai.heng.feng@canonical.com>
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
next prev parent reply other threads:[~2020-09-24 19:57 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 7:47 [Intel-wired-lan] [PATCH] e1000e: Power cycle phy on PM resume Kai-Heng Feng
2020-09-23 7:47 ` Kai-Heng Feng
2020-09-23 12:17 ` [Intel-wired-lan] " Andrew Lunn
2020-09-23 12:17 ` Andrew Lunn
2020-09-23 14:44 ` [Intel-wired-lan] " Kai-Heng Feng
2020-09-23 14:44 ` Kai-Heng Feng
2020-09-23 15:37 ` [Intel-wired-lan] " Andrew Lunn
2020-09-23 15:37 ` Andrew Lunn
2020-09-24 12:50 ` [Intel-wired-lan] " Kai-Heng Feng
2020-09-24 12:50 ` Kai-Heng Feng
2020-09-23 13:28 ` [Intel-wired-lan] " Paul Menzel
2020-09-23 13:28 ` Paul Menzel
2020-09-23 14:46 ` Kai-Heng Feng
2020-09-23 14:46 ` Kai-Heng Feng
2020-09-23 15:02 ` Paul Menzel
2020-09-23 15:02 ` Paul Menzel
2020-09-23 19:28 ` Andrew Lunn
2020-09-23 19:28 ` Andrew Lunn
2020-09-24 13:02 ` Paul Menzel
2020-09-24 13:02 ` Paul Menzel
2020-09-24 15:09 ` [Intel-wired-lan] [PATCH v2] e1000e: Increase iteration on polling MDIC ready bit Kai-Heng Feng
2020-09-24 15:09 ` Kai-Heng Feng
2020-09-24 15:32 ` [Intel-wired-lan] " Paul Menzel
2020-09-24 15:32 ` Paul Menzel
2020-09-24 16:04 ` Andrew Lunn
2020-09-24 16:04 ` Andrew Lunn
2020-09-24 15:53 ` Andrew Lunn
2020-09-24 15:53 ` Andrew Lunn
2020-09-24 16:04 ` [Intel-wired-lan] " Kai-Heng Feng
2020-09-24 16:04 ` Kai-Heng Feng
2020-09-25 8:50 ` [Intel-wired-lan] " David Laight
2020-09-25 8:50 ` David Laight
2020-09-25 13:29 ` [Intel-wired-lan] " Andrew Lunn
2020-09-25 13:29 ` Andrew Lunn
2020-09-26 10:08 ` [Intel-wired-lan] " David Laight
2020-09-26 10:08 ` David Laight
2020-09-24 16:45 ` [Intel-wired-lan] [PATCH v3] " Kai-Heng Feng
2020-09-24 16:45 ` Kai-Heng Feng
2020-09-24 19:57 ` Andrew Lunn [this message]
2020-09-24 19:57 ` Andrew Lunn
2020-09-25 3:57 ` [Intel-wired-lan] " Kai-Heng Feng
2020-09-25 3:57 ` Kai-Heng Feng
2020-09-25 5:16 ` [Intel-wired-lan] " Paul Menzel
2020-09-25 5:16 ` Paul Menzel
2020-09-28 8:36 ` [Intel-wired-lan] [PATCH v4] e1000e: Increase polling timeout on " Kai-Heng Feng
2020-09-28 8:36 ` Kai-Heng Feng
2020-09-29 13:08 ` [Intel-wired-lan] " Neftin, Sasha
2020-09-29 13:08 ` Neftin, Sasha
2020-09-29 13:31 ` Kai-Heng Feng
2020-09-29 13:31 ` Kai-Heng Feng
2020-09-29 13:46 ` Neftin, Sasha
2020-09-29 13:46 ` Neftin, Sasha
2020-09-29 15:08 ` Kai-Heng Feng
2020-09-29 15:08 ` Kai-Heng Feng
2020-09-29 15:11 ` David Laight
2020-09-29 15:11 ` David Laight
2020-09-29 15:12 ` Kai-Heng Feng
2020-09-29 15:12 ` Kai-Heng Feng
2020-09-30 6:54 ` Vitaly Lifshits
2020-09-30 6:54 ` Vitaly Lifshits
2020-10-05 6:23 ` Kai-Heng Feng
2020-10-05 6:23 ` Kai-Heng Feng
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=20200924195719.GF3821492@lunn.ch \
--to=andrew@lunn.ch \
--cc=intel-wired-lan@osuosl.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.