netdev - RE: Marvell Phy (1510) issue since v4.7 kernel

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]

Date:   Mon, 9 Jan 2017 23:48:18 +0000
From:   "Kwok, WingMan" <w-kwok2@...com>
To:     Andrew Lunn <andrew@...n.ch>,
        "Karicheri, Muralidharan" <m-karicheri2@...com>
CC:     "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: Marvell Phy (1510) issue since v4.7 kernel


Hi Andrew,


> -----Original Message-----
> From: Andrew Lunn [mailto:andrew@...n.ch]
> Sent: Monday, January 09, 2017 5:57 PM
> To: Karicheri, Muralidharan
> Cc: netdev@...r.kernel.org; Kwok, WingMan
> Subject: Re: Marvell Phy (1510) issue since v4.7 kernel
> 
> On Mon, Jan 09, 2017 at 05:38:39PM -0500, Murali Karicheri wrote:
> > Hello Charles-Antoine, Andrew,
> >
> > We have recently upgraded our kernel to v4.9 and started seeing an
> issue
> > on our Keystone EVMs (K2E/L) that uses Marvel Phy 1510. The issue is
> that
> > when we do a reboot command from the Linux console or do a SoC
> reset,
> > the DHCP times out at U-Boot due to Phy auto negotiation failure.
> This works
> > fine when the board is power cycled.
> 
> I've seen similar before. What version of kernel are you upgrading
> from?
> 
> The problem i've had is that on shutdown/reboot, linux powers the PHYs
> off. The uboot i have does not power them on again. Clearly a uboot
> issue, it should not assume the PHYs are powered on.
> 
> I work around this with a uboot command:
> 
> mii write 1 0 0x3100
> 
> where the PHY is at address 1 on the bus. This writes to register 0,
> and the import bit which needs setting to 0 is bit 11.
> 
> If mii read shows bit 11 is set, you know there uboot did not power up
> the PHY.
> 
>     Andrew

Thanks for the suggestion.

But when kernel is reboot into u-boot, "mii read 0 0" shows
0x1000, ie. bit 11 is 0, and still the phy auto-nego times out.

The "mii read 0 0" shows the same value 0x1000 if we power cycle
board and the phy auto-nego works fine.

Could there be some other registers that need to be re-configured?

We are upgrading from kernel v4.4 to v4.9. And the u-boot is 2016.05.

Regards,
WingMan