Hi > -----Original Message----- > From: Frank Schäfer <fschaefer.oss@xxxxxxxxxxxxxx> > Sent: Wednesday, August 17, 2022 4:18 AM > To: Ping-Ke Shih <pkshih@xxxxxxxxxxx>; linux-wireless@xxxxxxxxxxxxxxx > Subject: rtw88: "timed out to flush queue 1" > > I tried wireless-testing today to see if the recent rtw88 patches are > fixing the problems I'm facing with my rtw8821ce device. > The device now associates much faster and the tons of "failed to get tx > report from firmware" messages are gone. > However, the device disconnects very often and the log shows lots of > > [ 20.900786] rtw_8821ce 0000:02:00.0: timed out to flush queue 1 > > messages, which is new. > > > A typical section from the dmesg output: > ... > [ 13.099028] wlo1: authenticate with f8:d1:11:xx:xx:xx > [ 13.128833] wlo1: Allocated STA f8:d1:11:xx:xx:xx > [ 13.128846] wlo1: HE not supported, disabling HE and EHT > [ 13.128848] wlo1: EHT not supported, disabling EHT > [ 13.128849] wlo1: bad VHT capabilities, disabling VHT > [ 13.128852] wlo1: VHT operation missing / VHT not supported > [ 13.634812] wlo1: Inserted STA f8:d1:11:xx:xx:xx > [ 13.772803] wlo1: send auth to f8:d1:11:xx:xx:xx (try 1/3) > [ 13.775493] wlo1: authenticated > [ 13.775501] wlo1: moving STA f8:d1:11:xx:xx:xx to state 2 > [ 13.775676] rtw_8821ce 0000:02:00.0 wlo1: disabling HT/VHT/HE as > WMM/QoS is not supported by the AP > [ 13.812815] wlo1: HE not supported, disabling HE and EHT > [ 13.812822] wlo1: EHT not supported, disabling EHT > [ 13.812826] wlo1: HT operation missing / HT not supported Does your AP support HT or VHT? Can you change another AP that support VHT? > [ 14.318955] wlo1: associate with f8:d1:11:xx:xx:xx (try 1/3) > [ 14.561324] wlo1: associate with f8:d1:11:xx:xx:xx (try 2/3) > [ 14.571012] wlo1: RX AssocResp from f8:d1:11:xx:xx:xx (capab=0x431 > status=0 aid=1) > [ 14.571052] wlo1: moving STA f8:d1:11:xx:xx:xx to state 3 > [ 14.571208] wlo1: associated > [ 14.649252] IPv6: ADDRCONF(NETDEV_CHANGE): wlo1: link becomes ready > [ 14.649610] wlo1: moving STA f8:d1:11:xx:xx:xx to state 4 > [ 20.900786] rtw_8821ce 0000:02:00.0: timed out to flush queue 1 > [ 21.392784] rtw_8821ce 0000:02:00.0: timed out to flush queue 1 > [ 21.904779] rtw_8821ce 0000:02:00.0: timed out to flush queue 1 > [ 22.044770] rtw_8821ce 0000:02:00.0: timed out to flush queue 1 > [ 23.312776] rtw_8821ce 0000:02:00.0: timed out to flush queue 1 > [ 25.444803] rtw_8821ce 0000:02:00.0: timed out to flush queue 1 > [ 25.960816] rtw_8821ce 0000:02:00.0: timed out to flush queue 1 > [ 27.249290] wlo1: cancelling AP probe due to a received beacon > [ 31.168781] rtw_8821ce 0000:02:00.0: timed out to flush queue 1 > [ 31.604945] rtw_8821ce 0000:02:00.0: timed out to flush queue 1 > [ 32.572767] rtw_8821ce 0000:02:00.0: timed out to flush queue 1 > [ 33.832856] rtw_8821ce 0000:02:00.0: timed out to flush queue 1 > [ 36.461025] rtw_8821ce 0000:02:00.0: timed out to flush queue 1 > [ 37.405071] rtw_8821ce 0000:02:00.0: timed out to flush queue 1 > [ 37.889031] rtw_8821ce 0000:02:00.0: timed out to flush queue 1 > [ 39.641417] wlo1: cancelling AP probe due to a received beacon > [ 49.293315] wlo1: cancelling AP probe due to a received beacon > [ 58.861319] wlo1: cancelling AP probe due to a received beacon > [ 68.669330] wlo1: cancelling AP probe due to a received beacon > [ 78.205321] wlo1: cancelling AP probe due to a received beacon > [ 80.793042] wlo1: detected beacon loss from AP (missed 7 beacons) - > probing > [ 80.824424] wlo1: No ack for nullfunc frame to AP f8:d1:11:xx:xx:xx, > try 1/2 > [ 80.851851] wlo1: No ack for nullfunc frame to AP f8:d1:11:xx:xx:xx, > disconnecting. > [ 80.889060] wlo1: moving STA f8:d1:11:xx:xx:xx to state 3 > [ 80.905202] wlo1: moving STA f8:d1:11:xx:xx:xx to state 2 > [ 80.905230] wlo1: moving STA f8:d1:11:xx:xx:xx to state 1 > [ 80.905233] wlo1: Removed STA f8:d1:11:xx:xx:xx > [ 80.905338] wlo1: Destroyed STA f8:d1:11:xx:xx:xx > ... > > FW version is 24.11.0. > I tried with and without disable_lps_deep / disable_aspm, but that makes > no difference. > > Any ideas ? Anything I can do ? > It seems like link quality isn't good. Please turn off power saving by 'iw wlo1 set power_save off' to see if it can help. And, use 'iw wlo1 station dump' to check link quality. If 'signal:' is lower than -60, it will be bad. Ping-Ke
