netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Linton <jeremy.linton@arm.com>
To: Jamie Iles <jamie@nuviainc.com>, Andrew Lunn <andrew@lunn.ch>
Cc: netdev@vger.kernel.org, Calvin Johnson <calvin.johnson@oss.nxp.com>
Subject: Re: [PATCH] net/fsl: quieten expected MDIO access failures
Date: Thu, 24 Sep 2020 10:40:24 -0500	[thread overview]
Message-ID: <eafa77d6-4a00-f40e-a4fe-6b50736f3e03@arm.com> (raw)
In-Reply-To: <20200924151200.GW418386@poplar>

Hi,

On 9/24/20 10:12 AM, Jamie Iles wrote:
> Hi Andrew,
> 
> On Thu, Sep 24, 2020 at 05:04:53PM +0200, Andrew Lunn wrote:
>> On Thu, Sep 24, 2020 at 03:56:45PM +0100, Jamie Iles wrote:
>>> MDIO reads can happen during PHY probing, and printing an error with
>>> dev_err can result in a large number of error messages during device
>>> probe.  On a platform with a serial console this can result in
>>> excessively long boot times in a way that looks like an infinite loop
>>> when multiple busses are present.  Since 0f183fd151c (net/fsl: enable
>>> extended scanning in xgmac_mdio) we perform more scanning so there are
>>> potentially more failures.
>>>
>>> Reduce the logging level to dev_dbg which is consistent with the
>>> Freescale enetc driver.
>>
>> Hi Jamie
>>
>> Does the system you are using suffer from Errata A011043?
> 
> It's the HoneyComb SolidRun (LX2160A) and I can't find an errata list
> for that chip.  It's booting from ACPI in any case so wouldn't have that
> workaround set.

I don't see those messages, but granted my firmware is a bit out of 
date. Let me upgrade it and see if I can reproduce it too.

(also +CC Calvin)

  reply	other threads:[~2020-09-24 15:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-24 14:56 [PATCH] net/fsl: quieten expected MDIO access failures Jamie Iles
2020-09-24 15:04 ` Andrew Lunn
2020-09-24 15:12   ` Jamie Iles
2020-09-24 15:40     ` Jeremy Linton [this message]
2020-09-24 15:32 ` Andrew Lunn
2020-09-25  3:14 ` David Miller

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=eafa77d6-4a00-f40e-a4fe-6b50736f3e03@arm.com \
    --to=jeremy.linton@arm.com \
    --cc=andrew@lunn.ch \
    --cc=calvin.johnson@oss.nxp.com \
    --cc=jamie@nuviainc.com \
    --cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).