New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FS#631 - AR8327 switch link state change check not working on TL-WR1043ND v3 (QCA9558) #5633
Comments
VittGam: Hmmm... Obviously markdown syntax for blocks isn't supported here, but I can't see a way for me to edit the description...
BusyBox v1.26.2 () built-in shell (ash)
BusyBox v1.23.2 (2016-01-02 18:01:44 CET) built-in shell (ash)
|
storchi: same problem: #604 |
VittGam: Hmmm, I should re-test with my WDR3600 and WDR4300 then. I might have messed up with my tests on those routers, since I observed that it didn't happen on WDR4300... By the way, polling is not the solution here, since the switch sends the change notifications as IRQs, and the kernel picked them up correctly with OpenWrt CC 15.05.1 release (which does not seem to have that polling patch you linked)... |
VittGam: Oh and by the way, this problem does not happen on a TL-WR1043ND v4, which has a QCA956x SoC and an AR8337 rev 2 switch chip. |
VittGam:
Hello,
On my TP-LINK TL-WR1043ND v3 (ar71xx QCA9558) with today's LEDE snapshot, the AR8327 switch isn't sending port change interrupt events to the CPU.
The
ar8xxx_check_link_states
function intarget/linux/generic/files/drivers/net/phy/ar8216.c
is not being called at all, since not only the messages about port link status change aren't printed to the dmesg, but the ARL table isn't getting cleaned either. I don't understand why this is happening...This regression is not present in other routers with the same AR8327 switch chip (but rev. 2 instead of rev. 4), such as TP-LINK TL-WDR4300 v1 (ar71xx) and TP-LINK TL-WDR4900 v1 (mpc85xx).
(Latest LEDE stable release also does exibit the regression.)
Below you can see a session with LEDE; and a session with OpenWrt CC 15.05.1 release, which does not exibit the problem.
(The CC image is for the TL-WR1043ND v2, since v3 images weren't built yet at that time; v2 and v3 are the same hardware, as it can be seen from the FCC docs, where TP-LINK requested an ID change from v2 to v3.)
Please let me know if there's anything I can try to help debug this problem!
Cheers,
Vittorio
The text was updated successfully, but these errors were encountered: