netdev - Re: [BUG] The genet is not working

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <b68664e4-1b42-fc04-3b16-694b0e588b36@gmail.com>
Date:   Wed, 23 Jan 2019 20:47:38 -0800
From:   Florian Fainelli <f.fainelli@...il.com>
To:     Jaedon Shin <jaedon.shin@...il.com>,
        "David S. Miller" <davem@...emloft.net>
Cc:     netdev@...r.kernel.org, Andrew Lunn <andrew@...n.ch>,
        Heiner Kallweit <hkallweit1@...il.com>, opendmb@...il.com
Subject: Re: [BUG] The genet is not working



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