-
-
Notifications
You must be signed in to change notification settings - Fork 10.2k
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#2216 - ath79 - eth0 Spasmodic Link Speed After Driver Changes? - 841NDv9 #8243
Comments
gch981213: Would you mind to test if reverting only these two commits fixes your problem? 3d93b35 ath79: ag71xx: remove switch driver in ag71xx I don't have the actual hardware with me now and can't do any tests. Reverting the above two commits will switch back to old switch driver. |
Spider-Vice: Yes, I reverted my build to before those commits and it's working fine thus far. |
levin41: I can confirm this issue on a v8 with 19.07-rc1
As the cause seems to be known, maybe this should be fixed? |
Spider-Vice: Not sure if this commit (0d416a8) was an attempt at fixing the issue, but my trunk build built yesterday is still showing the issue if so. The only solutions for now are reverting those two April 2019 commits or going back to a build from back then. |
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 |
LinuxKernel1: Had the same problem on WA850RE & WA860RE (OpenWrt 19.07-SNAPSHOT, r11151-afaa978b74). git revert 3d93b35 --no-edit The link problems were easy to reproduce...just had to generate some higher load (e.g. a download via wifi with about 50 Mbit/s). Any more information needed to solve this? |
XDjackieXD: I can confirm the issue on latest master (7190fb2) on a Mikrotik LHG XL 2. The solution to revert the two commits mentioned by LinuxKernel1 also worked for me. |
gch981213: Here's a fix for this: |
Spider-Vice:
I've built the latest version of OpenWRT with stock packages and configuration, however, after random amounts of time, all clients lose connectivity because the eth0 link speed drops from the regular 100 Mbps Full Duplex to 10 Mbps Half Duplex, only to reconnect again after a couple of minutes (seconds to mintes, it depends), and do it again at another random time.
[18580.106696] eth0: link up (100Mbps/Full duplex)
[19014.825937] eth0: link up (10Mbps/Half duplex)
[19055.384105] eth0: link up (100Mbps/Full duplex)
[21927.853366] eth0: link up (10Mbps/Half duplex)
[22003.771999] eth0: link up (100Mbps/Full duplex)
[23743.685216] eth0: link down
[23744.723679] eth0: link up (100Mbps/Full duplex)
[23756.242265] eth0: link down
[23757.283590] eth0: link up (100Mbps/Full duplex)
[24075.522397] eth0: link up (10Mbps/Half duplex)
[24090.081802] eth0: link up (100Mbps/Full duplex)
[24100.481809] eth0: link up (10Mbps/Half duplex)
[24166.001178] eth0: link up (100Mbps/Full duplex)
[24500.880989] eth0: link up (10Mbps/Half duplex)
The logs aren't very useful, it seems. Both syslog and dmesg show the same.
I suspect this started happening after this series of commits (ending with this one) where there were driver changes to the switch, as it didn't happen before I recompiled a new build with all those newer changes:
3d93b35
The text was updated successfully, but these errors were encountered: