#19085: nanostation m5 loco xw "loses" interface
------------------------+------------------------
Reporter: anonymous | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone:
Component: kernel | Version: Trunk
Resolution: | Keywords:
------------------------+------------------------
Comment (by cmlara):
The 803x is the "ethernet subchip"(if you can call it that considering its
on the same SoC I'm confused as to why it gets its own designator, but it
apparently does)
The Actual SOC for the XW is a 934x (I'm not 100% sure what the x is on
the ones I'm working with at the moment as they are not right in front of
me but I'm wanting to say 9342 as well)
Regarding at803x not being used: that is my poin't, the kernel code I
think solves this lockup issue is in that module (and has been for a
while) but we(OpenWRT) are not calling itif I understand correctly meaning
when the node locks up it never gets reset.
Replying to [comment:33 leoso]:
> Replying to [comment:32 cmlara]:
> > I work with the one gentleman reporting the NanoBeam in [#comment:19]
as part of a larger project.
> >
> > As far as I/we can tell it affects the entire XW line (AR803x) EXCEPT
the NanoStation (Which has a built in switch)(There is a "NanoStation" and
"NanoStation Loco" for reference of those not familiar with the Ubiquiti
product lineup, the "NanoStation" non loco device is basically the only
device that does have a built in switch) (Its either it affects the whole
line or we happen to be getting multiple bugs at once that cause the same
failure)
>
> I see we have some problem here. When you talk about Loco XW line you
means AR803x. In my log file from {#coment:18] I read the line
>
> [ 0.000000] CPU0 revision is: 0001974c (MIPS 74Kc)
> [ 0.000000] SoC: Atheros AR9342 rev 2
>
> in boot log. Can you please give us your dmesg output with the SoC
information? Do we have different SoCs with the same bug?
>
> >
> > This would seem to agree with the kernel code already around in
[#comment:12] and the question is (I think) at the moment "is that code
actually being used" before we blame kernel (as module at803x is never
loaded on devices and instead the "ag" module is used) as that code is
basically the same as code in [#comment:8] and [#comment:9] just written
in GPIOD format.
> >
>
> At least for me having an AR9342 the driver at803x is not used but the
driver in linux-3.18.11/arch/mips/ath79/.
--
Ticket URL: <https://dev.openwrt.org/ticket/19085#comment:34>
OpenWrt <http://openwrt.org>
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-tickets
