FS#2730 - TL-WR841N v8 ath79 Link Unstable

[openwrt-bot]

levin41:

Probably related to https://bugs.openwrt.org/index.php?do=details&task_id=2216 which was reported almost a year ago. The bug is still not fixed though.

Are there any plans to fix it or will 18.06 be the last stable version for this and probably other devices?

[8451.981464] eth1: link up (100Mbps/Full duplex)
[37071.909045] eth1: link down
[37072.988861] eth1: link up (100Mbps/Full duplex)
[48492.291332] eth1: link up (10Mbps/Half duplex)
[48632.691559] eth1: link up (100Mbps/Full duplex)
[55697.449886] eth1: link down
[55698.491082] eth1: link up (100Mbps/Full duplex)
[62395.095374] eth1: link up (10Mbps/Half duplex)
[62507.411488] eth1: link up (100Mbps/Full duplex)
[62726.853998] eth1: link up (10Mbps/Half duplex)
[62732.053093] eth1: link up (100Mbps/Full duplex)
[71071.460663] eth1: link down
[71072.618285] eth1: link up (100Mbps/Full duplex)
[73435.556373] eth1: link down
[73436.597169] eth1: link up (100Mbps/Full duplex)
[73547.879987] eth1: link up (10Mbps/Half duplex)
[73558.277169] eth1: link up (100Mbps/Full duplex)
[74438.121970] eth1: link down
[74439.162824] eth1: link up (100Mbps/Full duplex)
[75341.889076] eth1: link up (10Mbps/Half duplex)
[75352.290230] eth1: link up (100Mbps/Full duplex)
[76274.772404] eth1: link down
[76275.813134] eth1: link up (100Mbps/Full duplex)

[openwrt-bot]

bjonglez:

Forum discussion: https://forum.openwrt.org/t/tl-wr841n-v8-ath79-link-unstable/52427

[openwrt-bot]

levin41:

19.07 final is running fine for almost 3 hours now with the old switch driver. No more connection drops.

The question is now, is there anybody on the OpenWRT team experienced enough with drivers to fix the issue or will you reinstate the old driver?

[openwrt-bot]

mgondium:

I'm also getting this problem on the WAN side of a 841N v9 when using the tiny ath79 build.
Going back to ath9k tiny makes it go away.

But in my case it's on the WAN side, not the switch.

[ 1.538053] ag71xx-mdio.1: Found an AR934X built-in switch [ 1.591382] eth0: Atheros AG71xx at 0xba000000, irq 5, mode: gmii [ 2.228506] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.1:04 [uid=004dd042, driver=Generic PHY] [ 2.238739] eth1: Atheros AG71xx at 0xb9000000, irq 4, mode: mii

[openwrt-bot]

bjonglez:

I just noticed that there are no factory or sysupgrade images for 19.07.0:

http://downloads.openwrt.org/releases/19.07.0/targets/ath79/tiny/
http://downloads.openwrt.org/releases/19.07.0/targets/ar71xx/tiny/

Which image are you using exactly? Self-built?

[openwrt-bot]

mgondium:

@baptiste

in my case, yes, I built my images from trunk, default config with just nano added.

[openwrt-bot]

levin41:

@PMGP it's also on the wan side for me but I think it might be a 5 port switch with wan being one port of that

@baptiste Jonglez I'm also running my own image. No issues for 20h now with the old switch driver on 19.07 final

[openwrt-bot]

mgondium:

@Levin

I think the 841N has two phy interfaces, the WAN is not a VLAN like for example, in the 1043ND.

[openwrt-bot]

levin41:

"The Atheros AR9341 is a highly integrated and feature-rich IEEE 802.11n 2x2 2.4 GHz System-on-a-Chip (SoC) for advanced WLAN platforms. It includes a MIPS 74Kc processor, five port IEEE 802.3 Fast Ethernet Switch with MAC/PHY [...]"

[openwrt-bot]

mefuckin:

TL-WR842N v3 under 19.07.1 ath79 build also has this issue on the WAN (eth1). AFAIK this is not a switch port but a separate phy interface. Moving back to ar7xxx target resolves the problem.

[openwrt-bot]

mgondium:

There were commits regarding the ag71 driver.
1e95f9b

Tested trunk today on the 841Nv9

[ 39.847833] eth0: link up (1000Mbps/Full duplex)
[ 39.853187] br-lan: port 1(eth0) entered blocking state
[ 39.858697] br-lan: port 1(eth0) entered disabled state
[ 39.864554] device eth0 entered promiscuous mode
[ 39.880864] br-lan: port 1(eth0) entered blocking state
[ 39.886356] br-lan: port 1(eth0) entered forwarding state
[ 42.337572] eth1: link up (100Mbps/Full duplex)
[ 1061.937695] eth1: link up (10Mbps/Half duplex)
[ 1099.377265] eth1: link up (100Mbps/Full duplex)

Almost thought it was fixed. eth1 is the WAN port.

[openwrt-bot]

acchiappawrt:

On v9 I had one port of the switch not reacting at all till a reboot.

[openwrt-bot]

adrianschmutzler:

v8 and v9 are totally different. Please don't mix them here. If you experience issues on a v9, please open a new bug report.

[openwrt-bot]

lw9eau:

Hi, I'm have the same issue.

tplink cpe220 v3 (OpenWrt 19.07.3 r11063-85e04e9f46)

Qualcomm Atheros QCA9533 ver 2 rev 0

Thank

[81834.557578] br-lan: port 1(eth1) entered disabled state
[81835.594706] eth1: link up (100Mbps/Full duplex)
[81835.599609] br-lan: port 1(eth1) entered blocking state
[81835.605093] br-lan: port 1(eth1) entered forwarding state
[82885.986062] eth1: link down
[82885.990081] br-lan: port 1(eth1) entered disabled state
[82887.027251] eth1: link up (100Mbps/Full duplex)
[82887.032023] br-lan: port 1(eth1) entered blocking state
[82887.037504] br-lan: port 1(eth1) entered forwarding state
[83591.100142] eth1: link up (10Mbps/Half duplex)
[83603.579855] eth1: link up (100Mbps/Full duplex)
[83720.057687] eth1: link down
[83720.061676] br-lan: port 1(eth1) entered disabled state
[83721.098979] eth1: link up (100Mbps/Full duplex)
[83721.103894] br-lan: port 1(eth1) entered blocking state
[83721.109377] br-lan: port 1(eth1) entered forwarding state
[96991.402515] eth1: link down
[96991.406876] br-lan: port 1(eth1) entered disabled state
[96992.443303] eth1: link up (100Mbps/Full duplex)
[96992.448108] br-lan: port 1(eth1) entered blocking state
[96992.453614] br-lan: port 1(eth1) entered forwarding state
[102147.684865] eth1: link up (10Mbps/Half duplex)
[102370.242133] eth1: link up (100Mbps/Full duplex)