Re: net80211: more steady Tx rate with MiRa (please test)
Hi Stefan, * Stefan Sperling wrote: > > Since I am knee-deep in Tx aggregation right now, I would like to delegate > testing of the diff below against plain -current to the community. > If some of you could test the diff below and report back to me I would > appreciate it. > You don't need to get numbers from wireshark for this if you don't want to. > Letting me know if Tx is faster or not and whether there are any perceived > regressions is sufficient. I tested your diff for the last two days and noticed a regression After some time one of the two things happens: * Transfer rates drop to 0. Directly visible if I run tcpbench, indirectly if I cannot work with the Network any longer. I waited for quite some time (> 10m) for something to happened, however, nothing changes. Then I restarted the interface. * My Thinkpad completely looses connection to my AP (Fritzbox) such that I have to take iwm0 down and run sh /etc/netstart iwm0. It happens when I work as usual (SSH, email, surfing, etc) and if I do nothing else then running tcpbench between the Thinkpad and a APU2 running 6.5. I run the diff with the following hardware on latest -current: iwm0 at pci2 dev 0 function 0 "Intel Dual Band Wireless-AC 8265" rev 0x78, msi iwm0: hw rev 0x230, fw ver 22.361476.0, address 7c:2a:31:4d:1c:b9 Cheers Matthias
Re: net80211: more steady Tx rate with MiRa (please test)
On Fri, Jun 14, 2019 at 01:01:58PM +0200, Matthias Schmidt wrote: > Hi Stefan, > > * Stefan Sperling wrote: > > > > Since I am knee-deep in Tx aggregation right now, I would like to delegate > > testing of the diff below against plain -current to the community. > > If some of you could test the diff below and report back to me I would > > appreciate it. > > You don't need to get numbers from wireshark for this if you don't want to. > > Letting me know if Tx is faster or not and whether there are any perceived > > regressions is sufficient. > > I tested your diff for the last two days and noticed a regression > After some time one of the two things happens: Are you sure these problem are introduced by this diff? I am quite certain that these symptoms must be unrelated. > * Transfer rates drop to 0. Directly visible if I run tcpbench, > indirectly if I cannot work with the Network any longer. I waited > for quite some time (> 10m) for something to happened, however, nothing > changes. Then I restarted the interface. > * My Thinkpad completely looses connection to my AP (Fritzbox) such that > I have to take iwm0 down and run sh /etc/netstart iwm0. > > It happens when I work as usual (SSH, email, surfing, etc) and if I do > nothing else then running tcpbench between the Thinkpad and a APU2 > running 6.5. > > I run the diff with the following hardware on latest -current: > > iwm0 at pci2 dev 0 function 0 "Intel Dual Band Wireless-AC 8265" rev 0x78, msi > iwm0: hw rev 0x230, fw ver 22.361476.0, address 7c:2a:31:4d:1c:b9 > > Cheers > > Matthias >
Re: net80211: more steady Tx rate with MiRa (please test)
Hi, * Stefan Sperling wrote: > On Fri, Jun 14, 2019 at 01:01:58PM +0200, Matthias Schmidt wrote: > > Hi Stefan, > > > > * Stefan Sperling wrote: > > > > > > Since I am knee-deep in Tx aggregation right now, I would like to delegate > > > testing of the diff below against plain -current to the community. > > > If some of you could test the diff below and report back to me I would > > > appreciate it. > > > You don't need to get numbers from wireshark for this if you don't want > > > to. > > > Letting me know if Tx is faster or not and whether there are any perceived > > > regressions is sufficient. > > > > I tested your diff for the last two days and noticed a regression > > After some time one of the two things happens: > > Are you sure these problem are introduced by this diff? > I am quite certain that these symptoms must be unrelated. The first problem also shows up without your diff, however, the reconnect happens a lot faster. I will spend some more time testing. Cheers Matthias
Re: net80211: more steady Tx rate with MiRa (please test)
On Fri, Jun 14, 2019 at 05:33:41PM +0200, Matthias Schmidt wrote: > Hi, > > * Stefan Sperling wrote: > > On Fri, Jun 14, 2019 at 01:01:58PM +0200, Matthias Schmidt wrote: > > > Hi Stefan, > > > > > > * Stefan Sperling wrote: > > > > > > > > Since I am knee-deep in Tx aggregation right now, I would like to > > > > delegate > > > > testing of the diff below against plain -current to the community. > > > > If some of you could test the diff below and report back to me I would > > > > appreciate it. > > > > You don't need to get numbers from wireshark for this if you don't want > > > > to. > > > > Letting me know if Tx is faster or not and whether there are any > > > > perceived > > > > regressions is sufficient. > > > > > > I tested your diff for the last two days and noticed a regression > > > After some time one of the two things happens: > > > > Are you sure these problem are introduced by this diff? > > I am quite certain that these symptoms must be unrelated. > > The first problem also shows up without your diff, however, the > reconnect happens a lot faster. I will spend some more time testing. This diff has no effect on management frames; it only affects transmit rate of data frames while in assocated state; association state is kept alive by received frames, not by frames being sent. I don't see how the diff could be causing either of your issues. They must have been present already. Check 'ifconfig iwn0 debug' and see which messages correlate to disconnects. You're probably running into known issues with background scan (sends deauth to old AP but never switches to new AP; stays dead until down/up) and/or dead AP detection (sends probe request to AP, never gets a response, drops to SCAN state, takes some time to find the AP again, reconnects).
Re: net80211: more steady Tx rate with MiRa (please test)
Hi, * Stefan Sperling wrote: > > This diff has no effect on management frames; it only affects transmit > rate of data frames while in assocated state; association state is > kept alive by received frames, not by frames being sent. > > I don't see how the diff could be causing either of your issues. > They must have been present already. > > Check 'ifconfig iwn0 debug' and see which messages correlate to disconnects. > You're probably running into known issues with background scan (sends deauth > to old AP but never switches to new AP; stays dead until down/up) and/or > dead AP detection (sends probe request to AP, never gets a response, drops > to SCAN state, takes some time to find the AP again, reconnects). Seems you were quite right. The first disconnect I had today was related to a firmware error. Cheers Matthias 2019-06-15T10:57:42.422Z sigma /bsd: iwm0: fatal firmware error 2019-06-15T10:57:42.422Z sigma /bsd: iwm0: RUN -> INIT 2019-06-15T10:57:42.592Z sigma /bsd: iwm0: begin active scan 2019-06-15T10:57:42.593Z sigma /bsd: iwm0: INIT -> SCAN 2019-06-15T10:57:45.797Z sigma /bsd: iwm0: end active scan 2019-06-15T10:57:45.797Z sigma /bsd: iwm0: - 00:1e:2a:e1:18:906 +17 54M ess privacy rsn "ChaosUnlimited"! 2019-06-15T10:57:45.798Z sigma /bsd: iwm0: - 12:62:e5:d1:fd:a96 +21 54M ess privacy rsn "DIRECT-A9-HP OfficeJet 5200"! 2019-06-15T10:57:45.798Z sigma /bsd: iwm0: - 1c:3a:de:64:90:5b 13 +18 54M ess privacy rsn "CelenoInitialAP64905B"! 2019-06-15T10:57:45.798Z sigma /bsd: iwm0: - 38:10:d5:79:a3:4a6 +21 54M ess privacy rsn "FRITZ!BS"! 2019-06-15T10:57:45.799Z sigma /bsd: iwm0: - 44:4e:6d:98:c6:176 +21 54M ess privacy rsn "FRITZ!Box 6490 Cable"! 2019-06-15T10:57:45.799Z sigma /bsd: iwm0: - 44:4e:6d:ec:3c:d31 +21 54M ess privacy rsn "FRITZ!Box 6490 Cable"! 2019-06-15T10:57:45.799Z sigma /bsd: iwm0: - 44:fe:3b:10:c5:dc1 +17 54M ess no! rsn! "Telekom_FON"! 2019-06-15T10:57:45.800Z sigma /bsd: iwm0: - 46:4e:6d:ec:3c:d31 +21 54M ess privacy rsn "FRITZ!"! 2019-06-15T10:57:45.800Z sigma /bsd: iwm0: - 54:67:51:3d:90:46 11 +49 54M ess privacy rsn "melbourne2016"! 2019-06-15T10:57:45.800Z sigma /bsd: iwm0: - 54:67:51:3d:90:c8 36 +35 54M ess privacy rsn "melbourne2016"! 2019-06-15T10:57:45.800Z sigma /bsd: iwm0: - 56:67:11:3d:90:46 11 +48 54M ess privacy rsn! "Unitymedia WifiSpot"! 2019-06-15T10:57:45.800Z sigma /bsd: iwm0: - 90:5c:44:24:40:fa 100 +21 54M ess privacy rsn "UPC6ED3663"! 2019-06-15T10:57:45.801Z sigma /bsd: iwm0: - 90:5c:44:24:41:03 11 +17 54M ess privacy rsn "UPC6ED3663"! 2019-06-15T10:57:45.801Z sigma /bsd: iwm0: - 90:5c:44:27:c6:1b6 +17 54M ess privacy rsn "UPC89142D1"! 2019-06-15T10:57:45.801Z sigma /bsd: iwm0: - 90:5c:44:cf:2c:e66 +17 54M ess privacy rsn "UPCE5AEF49"! 2019-06-15T10:57:45.802Z sigma /bsd: iwm0: - 90:5c:44:db:c8:e56 +19 54M ess privacy rsn "UPC877738E"! 2019-06-15T10:57:45.802Z sigma /bsd: iwm0: - 90:5c:44:dd:72:486 +17 54M ess privacy rsn "UPCA7A2229"! 2019-06-15T10:57:45.802Z sigma /bsd: iwm0: - 92:5c:14:24:41:03 11 +17 54M ess privacy rsn! "Unitymedia WifiSpot"! 2019-06-15T10:57:45.802Z sigma /bsd: iwm0: - ae:22:15:d0:db:bf 11 +17 54M ess privacy rsn! "Unitymedia WifiSpot"! 2019-06-15T10:57:45.803Z sigma /bsd: iwm0: - cc:ce:1e:8b:cf:d1 60 +31 54M ess privacy rsn "hs.ka.v01d"! 2019-06-15T10:57:45.803Z sigma /bsd: iwm0: + cc:ce:1e:8b:cf:d23 +46 54M ess privacy rsn "karlsruhe.v01d" 2019-06-15T10:57:45.803Z sigma /bsd: iwm0: - d4:21:22:53:3a:9b1 +17 54M ess privacy rsn "WLAN-604342"! 2019-06-15T10:57:45.804Z sigma /bsd: iwm0: - e0:28:6d:16:2b:18 11 +21 54M ess privacy rsn "FRITZ!Box 7490"! 2019-06-15T10:57:45.804Z sigma /bsd: iwm0: SCAN -> AUTH 2019-06-15T10:57:45.804Z sigma /bsd: iwm0: sending auth to cc:ce:1e:8b:cf:d2 on channel 3 mode 11g 2019-06-15T10:57:45.813Z sigma /bsd: iwm0: AUTH -> ASSOC 2019-06-15T10:57:45.813Z sigma /bsd: iwm0: sending assoc_req to cc:ce:1e:8b:cf:d2 on channel 3 mode 11g 2019-06-15T10:57:45.825Z sigma /bsd: iwm0: ASSOC -> AUTH 2019-06-15T10:57:50.549Z sigma /bsd: iwm0: AUTH -> SCAN 2019-06-15T10:57:53.682Z sigma /bsd: iwm0: end active scan 2019-06-15T10:57:53.682Z sigma /bsd: iwm0: - 00:1e:2a:e1:18:906 +18 54M ess privacy rsn "ChaosUnlimited"! 2019-06-15T10:57:53.682Z sigma /bsd: iwm0: - 44:4e:6d:ee:7e:ae1 +21 54M ess privacy rsn "FRITZ!Box 6490 Cable"! 2019-06-15T10:57:53.683Z sigma /bsd: iwm0: - 44:fe:3b:42:1d:22 11 +17 54M ess privacy rsn "WLAN-331218"! 2019-06-15T10:57:53.683Z sigma /bsd: iwm0: - 44:fe:3b:42:1d:24 11 +17 54M ess no! rsn! "Telekom_FON"! 2019-06-15T10:57:53.683Z sigma /bsd: iwm0: - 54:67:51:3d:90:46 11 +56 54M ess privacy rsn "melbourne2016"! 2019-06-15T10:57:53.683Z sigma /bsd: iwm
