From: Florian Fainelli <f.fainelli@gmail.com>
To: Jaedon Shin <jaedon.shin@gmail.com>,
"David S. Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
opendmb@gmail.com
Subject: Re: [BUG] The genet is not working
Date: Wed, 23 Jan 2019 20:47:38 -0800 [thread overview]
Message-ID: <b68664e4-1b42-fc04-3b16-694b0e588b36@gmail.com> (raw)
In-Reply-To: <48F4FFA7-FA93-4EA8-B458-22CA314FD91E@gmail.com>
On 1/23/19 8:17 PM, Jaedon Shin wrote:
> Hi,
>
> The genet of Broadcom MIPS 40nm platforms with internal PHY isn't working
> after v4.20-rc1, but 28nm ARM platforms or external PHY is working.
>
> [ 1.064000] bcmgenet 10430000.ethernet: configuring instance for internal PHY
> [ 1.068000] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
> [ 1.196000] bcmgenet 10430000.ethernet eth0: Link is Down
> [ 11.076000] Waiting up to 110 more seconds for network.
> [ 21.088000] Waiting up to 100 more seconds for network.
> [ 31.100000] Waiting up to 90 more seconds for network.
> [ 41.112000] Waiting up to 80 more seconds for network.
> [ 51.124000] Waiting up to 70 more seconds for network.
> [ 61.136000] Waiting up to 60 more seconds for network.
> [ 71.148000] Waiting up to 50 more seconds for network.
> [ 81.160000] Waiting up to 40 more seconds for network.
> [ 91.172000] Waiting up to 30 more seconds for network.
> [ 101.184000] Waiting up to 20 more seconds for network.
> [ 111.196000] Waiting up to 10 more seconds for network.
>
> I tried bisecting for this between v4.19 and v4.20-rc1, I found a problematic
> commit 6e2d85ec0559 ("net: phy: Stop with excessive soft reset").
Thanks Jaedon, we will try to come up with an appropriate fix for that
problem.
--
Florian
prev parent reply other threads:[~2019-01-24 4:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 4:17 [BUG] The genet is not working Jaedon Shin
2019-01-24 4:47 ` Florian Fainelli [this message]
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=b68664e4-1b42-fc04-3b16-694b0e588b36@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=jaedon.shin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=opendmb@gmail.com \
/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