[LEDE-DEV] [OpenWrt-Devel] [PATCH] [kernel] fix XW ethernet lockup ar71xx-ag71xx-ar803x

Joe Ayers joe at ayerscasa.com
Wed Nov 30 18:55:19 PST 2016


Felix,

We think this is an SOC level problem given the at803x and defect is
embedded in the AR93xx SOC.  This GPIO pin is believed to be in
silicon.  If so, the same GPIO across all hardware that uses this SOC.
   Specifically, for the Ubiquiti "AirMax" line, this SOC is relevant
to:

AirGrid HP M5 XW
NanoBridge M5 XW 16/19
NanoStation M5 Loco XW
PowerBeam M2 XW 400
PowerBeam M5 XW 300/400
PowerBeam M5 XW 620 (Rocket XW image but has newer flash chip and
needs write protect fix still)
Rocket M5 XW
Rocket Titanium M5 XW (for completeness, but we're not supporting this)
NanoStation M5 XW (this has an external switch chip somehow avoiding
the defect or other).

We have only been able to reproduce this failure on NanoBridge M5 XW
19 and the Loco NS M5 XW (in CC release).   A ~year ago the symptoms
occurred in CC builds in all models except NSM5-XW.    Presumably, you
had since committed a fix within the at803x driver for the ubnt
devices that appear to be working now?   Regardless, all these devices
are in scope (as could be other manufacturer's devices) to be included
in the fix at the SOC level.    Will the Lede staged commit catch all
these devices?

Joe AE6XE

On Wed, Nov 30, 2016 at 3:07 AM, Felix Fietkau <nbd at nbd.name> wrote:
> On 2016-11-27 01:19, Joe Ayers wrote:
>> From: Joe Ayers <ae6xe at arrl.net>
>>
>> Fixes 19085 nanostation m5 loco xw loses interface
>>
>> Signed-off-by: Joe Ayers        <ae6xe at arrl.net>
>> Signed-off-by: Trevor Paskett <k7fpv at aredn.org>
>> Signed-off-by: Darryl  Quinn    <k5dlq at aredn.org>
>> Signed-off-by: Conrad Lara     <kg6jei at aredn.org>
> This fix is somewhat hackish, because it pushes a workaround for one
> particular PHY in the ethernet driver, potentially affecting many more
> devices.
>
> I've added support for this PHY to the at803x driver, including GPIO
> reset support and enabled it for this device.
>
> I've pushed my changes to my LEDE staging tree at:
> https://git.lede-project.org/?p=lede/nbd/staging.git;a=summary
> git://git.lede-project.org/lede/nbd/staging.git
>
> Please test if this resolves the issues for you as well.
>
> Thanks,
>
> - Felix



More information about the Lede-dev mailing list