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#929 - mt7620 abysmal wifi performance #6268
Comments
psyborg55: fixed with |
mgondium: That's not it. |
psyborg55: why do i even care about that |
bjonglez: pmgp: actually, this patch has been introduced between 17.01.1 and 17.01.2, so it's possibly the source of the issue rather than the fix. Could you test reverting these commits in the lede-17.01 branch (one at a time) and see which one introduces the issue? psyborg55: please be respectful towards others, you're not being helpful. |
mgondium: Confirmed that on 17.01.0 and 17.01.1 there is no performance hit. Reverting the patches on trunk had no effect on restoring performance. (or maybe I did it wrong? the files were indeed gone from the patches folder). Meanwhile, these are the unique "rt2" patches on 17.01.02 that are not on 17.01.1:
I'll try to ditch them all on 17.01.2 and see how it goes. UPDATE: Again, removing the last 4 didn't improve things, must be somewhere else. UPDATE2: 17.01.1's My blunt approach is at an end here, this must be debugged by someone who understands the driver. |
psyborg55: removed |
mgondium: tested just now 17.01.1: ~82/~78 Mbps dl/ul no errors on log and changing channels doesn't mess up like trunk changed only the wireless configuration on your image:
|
psyborg55: use same settings when doing test, especially channel. 72/85 dl/ul in my case after reverting his mess-up |
mgondium: I used the same configuration on both. I got the same speeds from the unpatched 17.01.2 that got for your image. (~55 Mbps). I read that the mt7620 without heatsink has a thermal throttling issue with high wifi load. I'm looking into that. |
psyborg55: removed |
mgondium: Your second image reached ~55 Mbps and remained stable. Before testing I added a heatsink to the router's SoC, it gets quite toasty at load. |
psyborg55: trunk is not expected to have stability. performance is usually lower. my second image is trunk from about10 days ago with minor change nothing special. on chaos calmer speed is over 100Mbps |
mgondium: Since you mentioned it, I tried the CC image and got ~75 Mbps, stable with multiple clients. What a shame the best is in the past. It's not the first time that this LEDE/OpenWrt fork messes up radios. |
mgondium: At this point, trunk won't go past ~50 Mbps @ht40 and the radio will stall if more than one device connects to the AP (but still show on scans and allows to connect). |
psyborg55: maybe you could read dangowrt 's commit message before complaining about channel change, ha? https://git.lede-project.org/?p=source.git;a=commit;h=9eacb9d7fc0b4c921f8d2ec91a51f10d8c3ae12f "This makes the channel switching logic already look a bit more like |
namidairo: There was a bug introduced when LEDE pulled down the updated MT7260 patch from upstream mac80211 which might be causing this. Take a look at the patch linked from dangowrt's staging branch. (RT6352 was getting the wrong values set because of duplicated else if) |
psyborg55: that patch as well as others regarding rt6352 are irrelevant until this trac issue is closed: https://dev.openwrt.org/ticket/22086 |
amir-sabbaghi: I have found the commit that causes the drop in speed: lede-project/source@4314646 |
mgondium: @ close request Archer C20i HT40 |
drut: How this issue can be closed when MT7620 keeps crashing with latest releases? |
mgondium:
HT40 wifi throughput went from ~80 Mbps(LEDE 17.01.0) to ~3Mpbs (since LEDE 17.01.2 to trunk, 17.01.1 wouldn't build).
HT20 decreased from ~40 to ~10 Mbps.
device is archer C20i (mt7620a) on 2.4 GHz band, 5 Ghz is unsupported (mt7610E).
Log errors:
[ 9.197616] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 6352, rev 0500 detected
[ 9.205560] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 7620 detected
[ 304.206295] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[ 304.278242] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[ 306.059378] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 2
The text was updated successfully, but these errors were encountered: