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:   Tue, 10 Jan 2017 01:37:46 +0000
From:   "Kwok, WingMan" <w-kwok2@...com>
To:     Andrew Lunn <andrew@...n.ch>
CC:     "Karicheri, Muralidharan" <m-karicheri2@...com>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: Marvell Phy (1510) issue since v4.7 kernel



> -----Original Message-----
> From: Andrew Lunn [mailto:andrew@...n.ch]
> Sent: Monday, January 09, 2017 6:56 PM
> To: Kwok, WingMan
> Cc: Karicheri, Muralidharan; netdev@...r.kernel.org
> Subject: Re: Marvell Phy (1510) issue since v4.7 kernel
> 
> > 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.
> 
> O.K, not so simple then.
> 
> I suggest you dump all the registers, in both the good and bad state,
> and see how they differ.
> 
>     Andrew

From Marvell's brief description http://www.marvell.com/transceivers/alaska-gbe/,
it seems that 88E1510/1518 don't support fiber. Only 88E1512 does. In
that case, the fiber support patch is not applicable to 88E1510/1518.

I investigate a little more of the u-boot auto-nego time out
problem after reboot and found that the problem is caused by
marvell_read_status() which leaves the fiber page out because the
phydev->link is TRUE. But if fiber is not applicable to 88E1510/1518,
this is an invalid check.

Any suggestion?

WingMan

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ