linux-kernel - Re: [PATCH] arm64: defconfig: Change CONFIG_AT803X

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <e39c043d-d098-283d-97b0-2a44aefec2f1@free.fr>
Date:   Wed, 27 Nov 2019 09:47:37 +0100
From:   Marc Gonzalez <marc.w.gonzalez@...e.fr>
To:     Oliver Graute <oliver.graute@...il.com>
Cc:     Peng Fan <peng.fan@....com>, Anson Huang <anson.huang@....com>,
        dl-linux-imx <linux-imx@....com>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Florian Fainelli <f.fainelli@...il.com>,
        Andrew Lunn <andrew@...n.ch>,
        Russell King <rmk+kernel@...linux.org.uk>,
        André Draszik <git@...red.net>,
        Heiner Kallweit <hkallweit1@...il.com>
Subject: Re: [PATCH] arm64: defconfig: Change CONFIG_AT803X_PHY from m to y

On 26/11/2019 15:54, Oliver Graute wrote:

> this patch broke my imx8qm nfs setup. With the generic phy driver my
> board is booting fine. But with the AT803X_PHY=y enabled  I'm running
> into the following phy issue. So on my side it looks inverse as on
> yours. What is the best proposal to fix this?
> 
> [    5.550442] fec 5b040000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
> [    5.573206] Sending DHCP requests ...... timed out!
> [   95.339702] IP-Config: Retrying forever (NFS root)...
> [   95.348873] Atheros 8035 ethernet 5b040000.ethernet-1:06: attached PHY driver [Atheros 8035 ethernet] (mii_bus:phy_addr=5b040000.ethernet-1:06, irq=POLL)
> [   99.438443] fec 5b040000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
> [   99.461206] Sending DHCP requests ...... timed out!

Which DTS are you using?

I bet one dollar that 6d4cd041f0af triggered a latent bug in the DTS.

Regards.