Netdev List
 help / color / mirror / Atom feed
From: Jaedon Shin <jaedon.shin@gmail.com>
To: Florian Fainelli <f.fainelli@gmail.com>,
	"David S. Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
	Heiner Kallweit <hkallweit1@gmail.com>
Subject: [BUG] The genet is not working
Date: Thu, 24 Jan 2019 13:17:21 +0900	[thread overview]
Message-ID: <48F4FFA7-FA93-4EA8-B458-22CA314FD91E@gmail.com> (raw)

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

             reply	other threads:[~2019-01-24  4:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-24  4:17 Jaedon Shin [this message]
2019-01-24  4:47 ` [BUG] The genet is not working Florian Fainelli

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=48F4FFA7-FA93-4EA8-B458-22CA314FD91E@gmail.com \
    --to=jaedon.shin@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=hkallweit1@gmail.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