[Mostly Solved] R7800 stops responding to clients

Post new topic   Reply to topic    DD-WRT Forum Index -> Atheros WiSOC based Hardware
Goto page 1, 2, 3, 4, 5  Next
Author Message
e-
DD-WRT Novice


Joined: 11 Mar 2022
Posts: 16

PostPosted: Wed Apr 27, 2022 5:09    Post subject: [Mostly Solved] R7800 stops responding to clients Reply with quote
[edit 3]
It's now been 3 weeks and only 1 repeat. The only difference from the edits below is that I upgraded to r48786 (and then to r48810, r48897 and r48971). I'm writing this one off as a firmware (it was mentioned in the thread that recent changes could be the cause) issue and leaving it at that.
[/edit 3]

[edit 2]
The issue happened again, over a week after no repeats.... dmesg shows one of the previous messages again:
Code:

[684359.362034] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 59 tid 0
[684359.364235] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 59 tid 0
[684359.369735] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 59 tid 0
[684359.377414] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 59 tid 0
[684359.384238] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 59 tid 0
[684489.522519] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 58 tid 0
[684489.522553] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 58 tid 0
[684489.528715] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 58 tid 0
[684489.535924] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 58 tid 0
[684489.543366] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 58 tid 0
[684489.550593] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 58 tid 0
[684489.557868] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 58 tid 0
[684539.915415] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 61 tid 3
[684539.915449] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 61 tid 3
[684539.921594] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 61 tid 3
[684539.928897] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 61 tid 3
[684539.936193] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 61 tid 0
[684539.943474] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 61 tid 3
[684539.950816] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 61 tid 0
[684539.959666] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 61 tid 3
[684539.966345] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 61 tid 0
[684539.972638] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 61 tid 0

[/edit 2]

[edit]
Summary of the changes that seemed to have fixed the issue for me (but ultimately did not), going from what seems most likely to the least likely:

- Enabled Disassoc Low Ack on both 2.4 and 5GHz
- Reverted the 5GHz width to 80MHz (from 80+80MHz I had set as a test) - the 80+80 combinations are mostly invalid and the advantages of VHT80+80 or VHT160 over VHT80 are marginal
- Lowered the Sensitivity Range (ACK Timing) to 1350 (from 3150) - although BS says higher ACK Timing is not an issue, reading the full explanation from the wiki and other resources (including answers below) showed that it's not necessary to be that high for my case
- Lowered the 2.4GHz network's Beacon Interval to 300 (from 400) - my setup uses different SSIDs for 2.4 and 5GHz, I don't have neighboring networks sharing SSIDs or channels with mine, so no need to have different BIs
- Disabled RTS/CPS and RTS Threshold on both 2.4 and 5GHz - not necessary in AP mode
- Changed the Regulatory Domain to United States (from China) - not sure this is actually needed (I live in China), but my previous router was set to US so I decided to give this a try based on a comment below

After making these changes we've gone 6 days without the issue repeating, so I believe it is fixed. Thank you to those who commented on the post with great advice and explanations.
[/edit]

Hello,

I hope this is the right place to post this, please point me in the right direction otherwise.

So the background is: I’ve been using DD-WRT for about 6 years, started with a NetGear R6250 that worked pretty well for most of this time. I upgraded my broadband to 500Mbps down/50Mbps up (I can’t choose the upload speed) last year, but still kept the R6250 on it even though I knew it’d be the bottleneck in the setup.. And finally got a R7800 to replace it with this last March. The R7800 is really great, I was surprised to see how much more it can do compared to the R6250. My devices can sustain 300-500Mbps most of the time and this is fine for me.

However, there is this weird behavior happening that I cannot find answers for. From time to time (and especially whenever a device goes out of range, like when one of us leaves the apartment, but not only whenever someone leaves), the router will just stop responding for a while (so far we’ve noticed between 30 seconds to 10 minutes windows of this). The devices (a mix of Apple devices and others, all of them get hit by the issue) remain connected to wifi, but cannot connect to anything. The router does not reply to ping. After some time, it starts replying with very high latency (800-20000ms), then after some more time, it resumes working normally.

The first firmware I used was 48432, then tried 48567 and now it’s on 48646. All of these have had this behavior.

The first post/link with something similar to this that I’ve been able to find was this one, where there was a reply from Kong suggesting attempting to turn off U-APS to see if that’d fix it. I have tried, with this:

nvram set wlan0_uapsd=0
nvram set wlan1_uapsd=0
nvram set wl0_wme_apsd=off
nvram set wl1_wme_apsd=off
nvram commit
reboot

But the issue persists.

Then I found these posts: first, second, third that mention firmware issues that could cause this - I see dozens of dmesg messages like this:

Code:

[ 6305.782393] device eth1 left promiscuous mode
[ 6305.782492] br0: port 1(eth1) entered disabled state
[ 6305.796533] device wlan0 left promiscuous mode
[ 6305.796635] br0: port 2(wlan0) entered disabled state
[ 6305.807768] device wlan1 left promiscuous mode
[ 6305.811741] br0: port 3(wlan1) entered disabled state
[ 6305.921243] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 1
[ 6305.921328] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 1
[ 6305.927059] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 1
[ 6306.034714] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
[ 6306.034774] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
[ 6306.040600] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
[ 6306.460980] device br0 entered promiscuous mode
[ 6306.578868] dwmac1000: Master AXI performs any burst length
[ 6306.578911] ipq806x-gmac-dwmac 37400000.ethernet eth1: IEEE 1588-2008 Advanced Timestamp supported
[ 6306.583446] ipq806x-gmac-dwmac 37400000.ethernet eth1: registered PTP clock
[ 6306.634192] dwmac1000: Master AXI performs any burst length
[ 6306.634234] ipq806x-gmac-dwmac 37400000.ethernet eth1: IEEE 1588-2008 Advanced Timestamp supported
[ 6306.638705] ipq806x-gmac-dwmac 37400000.ethernet eth1: registered PTP clock
[ 6306.661159] br0: port 1(eth1) entered blocking state
[ 6306.661180] br0: port 1(eth1) entered disabled state
[ 6306.665431] device eth1 entered promiscuous mode
[ 6306.670268] br0: port 1(eth1) entered blocking state
[ 6306.674732] br0: port 1(eth1) entered forwarding state
[ 6306.686713] device br0 left promiscuous mode
[ 6306.689877] device br0 entered promiscuous mode
[ 6306.697832] device br0 left promiscuous mode
[ 6306.771165] ath: EEPROM regdomain: 0x809c
[ 6306.771173] ath: EEPROM indicates we should expect a country code
[ 6306.771178] ath: doing EEPROM country->regdmn map search
[ 6306.771183] ath: country maps to regdmn code: 0x52
[ 6306.771188] ath: Country alpha2 being used: CN
[ 6306.771191] ath: Regpair used: 0x52
[ 6306.771195] ath: regdomain 0x809c dynamically updated by user
[ 6306.771240] ath: EEPROM regdomain: 0x809c
[ 6306.771244] ath: EEPROM indicates we should expect a country code
[ 6306.771247] ath: doing EEPROM country->regdmn map search
[ 6306.771250] ath: country maps to regdmn code: 0x52
[ 6306.771254] ath: Country alpha2 being used: CN
[ 6306.771256] ath: Regpair used: 0x52
[ 6306.771260] ath: regdomain 0x809c dynamically updated by user
[ 6306.820110] br0: port 1(eth1) entered disabled state
[ 6307.689921] ipq806x-gmac-dwmac 37400000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off
[ 6307.689975] br0: port 1(eth1) entered blocking state
[ 6307.697765] br0: port 1(eth1) entered forwarding state
[ 6309.849703] ath10k_pci 0000:01:00.0: wmi command 36872 timeout, restarting hardware
[ 6309.849743] ath10k_pci 0000:01:00.0: ani_enable failed from debugfs: -11
[ 6309.889711] ath10k_pci 0000:01:00.0: cannot restart a device that hasn't been started
[ 6312.418454] ath10k_pci 0000:01:00.0: boot get otp board id result 0x00040400 board_id 1 chip_id 0 ext_bid_support 1
[ 6312.470956] ath10k_pci 0000:01:00.0: boot upload otp to 0x1234 len 9315
[ 6316.034835] ath10k_pci 0000:01:00.0: Init Max Stations to 512
[ 6316.111330] ath10k_pci 0000:01:00.0: wmi event ready sw_version 0x01000000 abi_version 3 mac_addr 12:34:56:78:90:12 status 0
[ 6316.236018] ath10k_pci 0000:01:00.0: bdf failsafe status event received from fw: 0
[ 6316.243697] br0: port 2(wlan0) entered blocking state
[ 6316.243722] br0: port 2(wlan0) entered disabled state
[ 6316.247988] device wlan0 entered promiscuous mode
[ 6317.144381] br0: port 2(wlan0) entered blocking state
[ 6317.144406] br0: port 2(wlan0) entered forwarding state
[ 6320.249690] ath10k_pci 0001:01:00.0: wmi command 36872 timeout, restarting hardware
[ 6320.249734] ath10k_pci 0001:01:00.0: ani_enable failed from debugfs: -11
[ 6320.289748] ath10k_pci 0001:01:00.0: cannot restart a device that hasn't been started
[ 6322.777928] ath10k_pci 0001:01:00.0: boot get otp board id result 0x00040800 board_id 2 chip_id 0 ext_bid_support 1
[ 6322.830669] ath10k_pci 0001:01:00.0: boot upload otp to 0x1234 len 9315
[ 6326.381655] ath10k_pci 0001:01:00.0: Init Max Stations to 512
[ 6326.460198] ath10k_pci 0001:01:00.0: wmi event ready sw_version 0x01000000 abi_version 3 mac_addr 00:03:7f:12:34:56 status 0
[ 6326.649967] ath10k_pci 0001:01:00.0: bdf failsafe status event received from fw: 0
[ 6326.657302] br0: port 3(wlan1) entered blocking state
[ 6326.657326] br0: port 3(wlan1) entered disabled state
[ 6326.661885] device wlan1 entered promiscuous mode
[ 6326.666640] br0: port 3(wlan1) entered blocking state
[ 6326.671324] br0: port 3(wlan1) entered forwarding state
[ 6326.681380] br0: port 3(wlan1) entered disabled state
[ 6327.025017] br0: port 3(wlan1) entered blocking state
[ 6327.025041] br0: port 3(wlan1) entered forwarding state
[ 6327.311694] ksmbd: kill command received
[ 6328.027740] Linux kernel CIFS/SMB SERVER 3.4.4 by Namjae Jeon <linkinjeon@kernel.org>
[59929.358883] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[59929.358918] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[59929.366130] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[59929.374250] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[60232.383948] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[60232.383984] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[60232.391160] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[60232.399268] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[60787.441247] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[60787.441281] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[60802.442631] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[60802.442666] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[60970.463021] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[60970.463054] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[60970.470253] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[60970.478338] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[61249.506683] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[61249.506716] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[61249.513920] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[61249.522074] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[61255.507549] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[61255.507581] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[61255.514803] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[61255.522934] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[61696.557534] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[61696.557567] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[61696.564756] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[61696.572909] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[63919.768227] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[63919.768261] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[63919.775445] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[63919.783596] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[64438.802214] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[64438.802246] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[64438.809439] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[64438.817645] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[70469.558986] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[70469.559020] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[70469.566219] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[70469.574371] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[77676.326130] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[77676.326162] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[77919.355709] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[77919.355742] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[77919.362923] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[77919.371075] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[79236.501901] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[79236.501934] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[79236.509182] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[79236.517299] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[80073.606446] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[80073.606479] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[80073.613705] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[80073.621838] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[80529.657772] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[80529.657805] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[80529.664983] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[80529.673191] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[81012.703326] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[81012.703360] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[81012.710548] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[81012.718660] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[81063.708083] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[81063.708119] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[81063.715329] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[81063.723489] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[81447.748336] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[81447.748369] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[81447.755571] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[81447.763723] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[81630.765351] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[81630.765385] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[81630.772593] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[81630.780733] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[82950.905429] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[82950.905462] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[82950.912657] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[82950.920809] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[85492.189338] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[85591.198022] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[85591.198055] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[85591.205294] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[85591.213415] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[85849.222950] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[85849.222983] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[85849.230180] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[85849.238264] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[86203.253536] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[86203.253568] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[86203.260760] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[86203.268856] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[86305.267619] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[86305.267653] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[86305.274855] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[86305.283005] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[87589.410979] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[87589.411076] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[87589.418213] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[87589.426450] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[87604.413475] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[87604.413508] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[87604.420713] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[87604.428794] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[88822.528006] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[88822.528038] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[88822.535229] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[88822.543381] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[88822.551546] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[88924.538286] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[88924.538319] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[88924.545552] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[88924.553678] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[89095.553457] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[89095.553492] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[89095.560676] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[89095.568786] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[89140.557523] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[89140.557556] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[89140.564792] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[89140.572905] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[90664.725441] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[90664.725477] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[90664.732694] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[90664.740815] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[90694.728556] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[90694.728609] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[90694.735824] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[90694.743966] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[90709.730372] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[90709.730407] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[91165.780988] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[91165.781021] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[91165.788146] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[91165.796374] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[91711.828590] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[91711.828623] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[91711.835826] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[91711.843993] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[92764.914117] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[92764.914150] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[92764.921392] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[92764.929528] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[93467.017664] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[93467.017696] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[93467.024891] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[93467.033044] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[94205.092045] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[94205.092078] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[94205.099304] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[94205.107450] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[94211.092532] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[94211.092567] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[94211.099718] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[94211.107949] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[94211.116096] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[95273.188261] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[95273.188296] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[95273.195481] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[95273.203635] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[95273.211788] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[95273.219942] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[111780.836535] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[111780.836567] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[111780.843765] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[129393.009924] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[129393.009958] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[129393.017080] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[129393.025415] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[129393.033659] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[138019.335691] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[138019.335724] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[138019.342953] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[138019.351198] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[141736.893843] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[141736.893876] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[141736.901087] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[141736.909247] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[143345.150078] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[143345.150113] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[143345.157235] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[143345.165558] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[145760.504070] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[145760.504103] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[145760.511308] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[145760.519472] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[145967.536357] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[145967.536390] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[145967.543619] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[145967.551831] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[153981.499973] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[153981.500007] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[153981.507206] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[153981.515462] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[153981.523728] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[153981.531944] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[154542.561502] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[154542.561534] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[154542.568657] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[154542.576989] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[156165.737782] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[156165.737814] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[156165.745004] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[156165.753250] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[156933.828139] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[156933.828172] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[156933.835373] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[156933.843621] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[160858.231989] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[160858.232022] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[160858.239164] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[160858.247453] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[162913.395958] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[162913.395992] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[162913.403188] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[162913.411432] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[162913.419607] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[164797.530430] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[164797.530461] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[164797.537668] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[164797.545939] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[167239.786659] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[167239.786693] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[167239.793904] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[167239.802138] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[167422.803740] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[167422.803773] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[167422.810964] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[167422.819186] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168691.966470] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168691.966507] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168691.973715] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168691.981951] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[169202.019671] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[169202.019703] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[169202.026930] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[169202.035168] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[171416.274411] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[171416.274443] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[171416.281645] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[171416.289902] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[171464.278512] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[171464.278547] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[171464.285759] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[171464.293971] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[171875.313519] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[171875.313551] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[171875.320738] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[171875.328926] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[173606.502350] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[173606.502383] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[173606.509579] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[173606.517779] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[174014.535541] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[174014.535574] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[174014.542817] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[174014.551060] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[174203.551778] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[174203.551809] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[174203.558933] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[174203.567241] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[175289.633075] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[175289.633108] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[175289.640342] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[175289.648502] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[176180.681834] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[176180.681866] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[176180.689031] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[176180.697328] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[176483.699203] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[176483.699236] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[176483.706426] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[176483.714671] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[177644.777045] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[177644.777079] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[177644.784300] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[177644.792540] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[178406.842221] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[178406.842254] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[178406.849398] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[178406.857694] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[178889.876312] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[178889.876346] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[178889.883545] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[178889.891760] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[183414.297553] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[183414.297588] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[183414.304814] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[183414.313051] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[183414.321275] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[195475.306241] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[195475.306279] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[195475.313512] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[195475.321744] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[224807.003999] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[224807.004033] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[224807.011237] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[224807.019404] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[247439.902265] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 6 tid 0
[247439.902306] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 6 tid 0
[247439.908475] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 6 tid 0
[247439.915647] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 6 tid 0
[247439.922864] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 6 tid 0
[247439.930402] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 6 tid 0
[247439.937254] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 6 tid 0
[247439.944537] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 6 tid 0
[247439.952042] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 6 tid 0
[247439.958881] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 6 tid 0


The last 2 kinds (“received unexpected tx_fetch_ind event” and “failed to lookup txq for peer_id X tid Y”) seem to always show up around when the issue happens.

I have tried to plug a computer to a LAN port whenever this happens, and that computer works fine via LAN even while the others cannot use wifi. The status page for the R7800 doesn’t show anything clearly abnormal when that happens, but dmesg shows dozens of messages as described above.

I have also tried different channels and widths, no success. The Status page’s surveys say that the quality should be fine (it stays in the 96-99% range, including whenever the issue happens) and I do not see any neighboring networks using the same name/channel as mine.

Is there anything else I can do to either find out more useful information, or to fix this?

Thank you.


Last edited by e- on Sat May 28, 2022 10:09; edited 3 times in total
Sponsor
egc
DD-WRT Guru


Joined: 18 Mar 2014
Posts: 12837
Location: Netherlands

PostPosted: Wed Apr 27, 2022 6:17    Post subject: Reply with quote
Things to try:

Use 80 MHz channel width instead of 80+80

Try another regulatory domain

But more importantly do you have 802.11r (FT) support enabled (on Wireless security page) if so disable it and perhaps give your radio's a different SSID

_________________
Routers:Netgear R7000, R6400v1, R6400v2, EA6900 (XvortexCFE), E2000, E1200v1, WRT54GS v1.
Install guide R6400v2, R6700v3,XR300:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=316399
Install guide R7800/XR500: https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=320614
Forum Guide Lines (important read):https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=324087
e-
DD-WRT Novice


Joined: 11 Mar 2022
Posts: 16

PostPosted: Wed Apr 27, 2022 6:26    Post subject: Reply with quote
I had been using 80MHz until last week, changed to 80+80 to see if it'd make a difference, but it hasn't. I'll revert to 80.

I'll try changing the regulatory domain (thinking back, the R2650 is set to US even though I was already in China when I got it, so could be that) to see if there is any effect.

And lastly, no, 802.11r is disabled on both 2.4 and 5GHz.

Thanks for the feedback, I'll try those and come back with results in a couple of days.
ho1Aetoo
DD-WRT Guru


Joined: 19 Feb 2019
Posts: 2927
Location: Germany

PostPosted: Wed Apr 27, 2022 7:24    Post subject: Reply with quote
use as already said 80Mhz channel width.
for VHT80+80 the channels are not filtered properly at the moment and it shows all kinds of "invalid" combinations
see : https://svn.dd-wrt.com/ticket/6965#comment:164

apart from this, the advantages of VHT80+80 and VHT160 over VHT80 are marginal
(almost no speed increase, and is supported by very very few clients).

You should enable "Disassoc Low Ack".
Disabling the option can lead to the mentioned problems (when a client moves out of range it blocks the whole network).
e-
DD-WRT Novice


Joined: 11 Mar 2022
Posts: 16

PostPosted: Wed Apr 27, 2022 7:55    Post subject: Reply with quote
ho1Aetoo wrote:
use as already said 80Mhz channel width.
for VHT80+80 the channels are not filtered properly at the moment and it shows all kinds of "invalid" combinations
see : https://svn.dd-wrt.com/ticket/6965#comment:164

apart from this, the advantages of VHT80+80 and VHT160 over VHT80 are marginal
(almost no speed increase, and is supported by very very few clients).

You should enable "Disassoc Low Ack".
Disabling the option can lead to the mentioned problems (when a client moves out of range it blocks the whole network).


Ahh, that may be it, then.

I had already reverted to 80MHz as I mentioned in my previous reply, and changed the regulatory domain to US. After reading your comment I enabled Disassoc Low Ack.

Thank you, I'll keep monitoring.
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 14125
Location: Texas, USA

PostPosted: Wed Apr 27, 2022 15:45    Post subject: Reply with quote
You don't necessarily need RTS/CTS in AP modes - and you need to know what the hardware supports if you enable it, 3150 ACK timing is high, not to mention your BI numbers.
_________________
"Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT
Pogo - A minimal level of ability is expected and needed...
DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)

----------------------
Linux User #377467 counter.li.org / linuxcounter.net
e-
DD-WRT Novice


Joined: 11 Mar 2022
Posts: 16

PostPosted: Wed Apr 27, 2022 21:28    Post subject: Reply with quote
kernel-panic69 wrote:
You don't necessarily need RTS/CTS in AP modes - and you need to know what the hardware supports if you enable it, 3150 ACK timing is high, not to mention your BI numbers.


I set all of those following the wiki and the stickied best settings post, and probably influenced by other links I didn't save.

What would be better settings for them?

By the way, I am seeing progress. Since making the changes suggested earlier, we've had no repeats of the issue and I see some of the “received unexpected tx_fetch_ind event” messages in dmesg, but none of the “failed to lookup txq for peer_id X tid Y”. I think it's early to call victory, but I think something is going in the right direction.
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 14125
Location: Texas, USA

PostPosted: Thu Apr 28, 2022 2:12    Post subject: Reply with quote
Using those recommendations wouldn't allow me to use the internet on any wifi device on my network (because an AP is not a client).

"As far as I know though, both these settings only affect the transmitter, i.e. configuring them on the AP only makes the AP use them for its transmissions and doesn't make the clients use them for their transmissions."

(from wiki linked article)

The problem with that linked servervault article is that doesn't completely take into account that wifi is not wired ethernet.

https://itectec.com/network/the-802-11-mtu/

_________________
"Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT
Pogo - A minimal level of ability is expected and needed...
DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)

----------------------
Linux User #377467 counter.li.org / linuxcounter.net
e-
DD-WRT Novice


Joined: 11 Mar 2022
Posts: 16

PostPosted: Thu Apr 28, 2022 2:37    Post subject: Reply with quote
kernel-panic69 wrote:
Using those recommendations wouldn't allow me to use the internet on any wifi device on my network (because an AP is not a client).

"As far as I know though, both these settings only affect the transmitter, i.e. configuring them on the AP only makes the AP use them for its transmissions and doesn't make the clients use them for their transmissions."

(from wiki linked article)

The problem with that linked servervault article is that doesn't completely take into account that wifi is not wired ethernet.

https://itectec.com/network/the-802-11-mtu/


Ok, so RTS/CTS isn't needed, I can turn it off, thank you. Also, should I disable RTS Threshold?

How about the ACK timing and BI? The wiki and other posts seem to suggest that the defaults are too low for them. That's why I went with the values I found on the related links.

For ACK Timing I've decided to lower it to 1350 based on the longer description on the wiki, but I'm willing to play around based on more experienced people's advice.

For BI, both wiki and the best settings sticky seem to agree at 300 (my router is not connected to other routers, at least for the foreseeable future, and I use separate SSIDs for 2.4 and 5GHz). So the change here is that I set the 2.4GHz one down to 300 as well (I don't have any devices that have both setup, only a couple of older devices that can only do 2.4GHz). But again, I do not know enough to set my foot either way, if you have better advice I'm open to it.
ho1Aetoo
DD-WRT Guru


Joined: 19 Feb 2019
Posts: 2927
Location: Germany

PostPosted: Thu Apr 28, 2022 8:18    Post subject: Reply with quote
has nothing to do with your problem ...
The beacon interval simply specifies how often beacon frames are sent.
These simply announce the presence of a wireless network.

more beacons = clients see the AP faster (but more overhead)
less beacons = clients see the AP later (but less overhead)

also works fine with a beacon interval of 100 and DTIM2 (which is pretty much the default setting)

and the optimal value for ACK timing depends on the distance between client and AP.
The value is not given in meters for nothing

long distance = high ACK timing value
short distance = low ACK timing value

high values are uproblematic because in case of a problem they only have a negative effect on the throughput (because the sender waits too long before starting a retransmission).
too low values on the other hand can make the link unusable


and CTS/RTS is ideally used on AP and client.
there simply corresponding frames are exchanged ( request to send , clear to send) to avoid collisions Smile

and the RTS threshold simply specifies at which packet size the frames will be sent
e-
DD-WRT Novice


Joined: 11 Mar 2022
Posts: 16

PostPosted: Thu Apr 28, 2022 8:42    Post subject: Reply with quote
ho1Aetoo wrote:
has nothing to do with your problem ...
The beacon interval simply specifies how often beacon frames are sent.
These simply announce the presence of a wireless network.

more beacons = clients see the AP faster (but more overhead)
less beacons = clients see the AP later (but less overhead)

also works fine with a beacon interval of 100 and DTIM2 (which is pretty much the default setting)

and the optimal value for ACK timing depends on the distance between client and AP.
The value is not given in meters for nothing

long distance = high ACK timing value
short distance = low ACK timing value

high values are uproblematic because in case of a problem they only have a negative effect on the throughput (because the sender waits too long before starting a retransmission).
too low values on the other hand can make the link unusable


and CTS/RTS is ideally used on AP and client.
there simply corresponding frames are exchanged ( request to send , clear to send) to avoid collisions Smile

and the RTS threshold simply specifies at which packet size the frames will be sent


Got it, thank you for the explanation.

If I understood it correctly, I think for my case these settings should be ok - the network has 3-12 devices, range we expect to be able to use it is < 50m and as I said in the OP, the 300-500Mbps we've been getting consistently is fine for us.

I'll keep watching the issue (second day of no occurrences) and I'll update the OP with the findings once I conclude the problem is fixed.

Thank you all for the insights!
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 14125
Location: Texas, USA

PostPosted: Thu Apr 28, 2022 16:17    Post subject: Reply with quote
Feel free to compare errors on wireless status page with whatever combination of settings you choose. I have a piece of crap TL-WR940Nv3 serving public wifi with mixed clients and nobody is bitching about quality of the wifi - I am not using the "recommended settings" because all they did was create issues. Some folks forget that they themselves argued the point that the sticky and wiki recommendations were bunk, lol.
_________________
"Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT
Pogo - A minimal level of ability is expected and needed...
DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)

----------------------
Linux User #377467 counter.li.org / linuxcounter.net
e-
DD-WRT Novice


Joined: 11 Mar 2022
Posts: 16

PostPosted: Thu Apr 28, 2022 23:29    Post subject: Reply with quote
kernel-panic69 wrote:
Feel free to compare errors on wireless status page with whatever combination of settings you choose. I have a piece of crap TL-WR940Nv3 serving public wifi with mixed clients and nobody is bitching about quality of the wifi - I am not using the "recommended settings" because all they did was create issues. Some folks forget that they themselves argued the point that the sticky and wiki recommendations were bunk, lol.


🤣 indeed. I understand that it'd be very complex to keep updated information for every setting under every possible scenario, so I look at the answers as "recommended for whoever-wrote-this' situation in that specific point in time".

My only wish was that either the settings themselves or the documentation were clearer about what they do. For example, the one that might have caused my issue ("Disassoc Low Ack"), I actually cannot find anything on the wiki about it. Only 2 forum posts and a question from you on SVN. If I recall correctly, my thought when I disabled it was something like "well, if I can't even find anything about it, I guess it's not actually needed".. And that was wrong.
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 14125
Location: Texas, USA

PostPosted: Fri Apr 29, 2022 0:08    Post subject: Reply with quote
Looks like Disassociate on Low Ack was never documented in the wiki Rolling Eyes I didn't even look to see if it was ever discussed in the forum as I requested on that ticket... whoops.
_________________
"Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT
Pogo - A minimal level of ability is expected and needed...
DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)

----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Alozaros
DD-WRT Guru


Joined: 16 Nov 2015
Posts: 6410
Location: UK, London, just across the river..

PostPosted: Fri Apr 29, 2022 8:51    Post subject: Reply with quote
kernel-panic69 wrote:
Looks like Disassociate on Low Ack was never documented in the wiki Rolling Eyes I didn't even look to see if it was ever discussed in the forum as I requested on that ticket... whoops.


hmm i used to use Disassociate on Low Ack, than decided to stop using it, as i had some clients dropping out, but not stalling the network...

I did do my homework back in the days and had to fiddle with low ack times too...as meaning of 'low ack' could be clients specific...
For the record, i do have R7800 and its been used/abused by various WiFi clients form different vendors, and its working ok...without Disassociate on Low Ack, ATM ...
The only thing that pops into my mind is, if you have a bad client with bad drivers...contributing towards this behaviour...

i did also fiddle with those values too, and some of those ware changed by default on the nowadays builds...in order to improve the situation...

tcp_low_latency = 1
tcp_timestamps = 0
tcp_tw_recycle = 0
tcp_tw_reuse = 0
tcp_slow_start_after_idle = 0

_________________
Atheros
TP-Link WR740Nv1 ---DD-WRT 55179 WAP
TP-Link WR1043NDv2 -DD-WRT 55303 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55460 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55460 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55363 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
Goto page 1, 2, 3, 4, 5  Next Display posts from previous:    Page 1 of 5
Post new topic   Reply to topic    DD-WRT Forum Index -> Atheros WiSOC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum