All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Patrick Häcker" <pat_h@web.de>
To: iwd@lists.linux.dev
Subject: Sometimes RxBitrate of 1000 Kbit/s
Date: Sun, 06 Nov 2022 15:36:11 +0100	[thread overview]
Message-ID: <5893463.lOV4Wx5bFT@mmm> (raw)

[-- Attachment #1: Type: text/plain, Size: 3921 bytes --]

Hello all,

from time to time my RxBitrate (sometimes the TxBitrate, too) goes down to
1000 Kbit/s, whereas it otherwise is in the usual 5 to 6 digit range. This
seems to especially happen some time after waking up from standby (S3), maybe
also from hibernate (S4).

When it happens, wireless usage is super slow to non-existent.

Restarting iwd immediately solves the problem. I routinely also reloaded the
involved kernel modules, but I think this was unnecessary as I
skipped it the last few times and only restarted iwd and this was enough to
get it back to a working state.

Naturally, it seems to occur every few hours, but I might be able to trigger
it more often with extensive standby cycles, but I am not sure.

That's how it looks when it happens (although TxBitrate is often still in the
normal 5 to 6 digit rate; please note ExpectedThroughput being much larger
than TxBitrate or RxBitrate):
# iwctl station wlan0 show
                                 Station: wlan0
--------------------------------------------------------------------------------
  Settable  Property              Value
--------------------------------------------------------------------------------
            Scanning              no
            State                 connected
            Connected network     *redacted*
            IPv4 address          192.168.0.10
            ConnectedBss          98:9b:cb:4b:b1:cc
            Frequency             2412
            Security              WPA3-Personal
            RSSI                  -44 dBm
            AverageRSSI           -55 dBm
            TxBitrate             1000 Kbit/s
            RxBitrate             1000 Kbit/s
            ExpectedThroughput    56906 Kbit/s

This is how it looks after restarting iwd:
# systemctl restart iwd
# iwctl station wlan0 show
                                 Station: wlan0
--------------------------------------------------------------------------------
  Settable  Property              Value
--------------------------------------------------------------------------------
            Scanning              no
            State                 connected
            Connected network     *redacted*
            IPv4 address          192.168.0.10
            ConnectedBss          98:9b:cb:4b:b1:cd
            Frequency             5180
            Security              WPA3-Personal
            RSSI                  -72 dBm
            AverageRSSI           -72 dBm
            RxMode                802.11n
            RxMCS                 9
            TxMode                802.11n
            TxMCS                 3
            TxBitrate             60000 Kbit/s
            RxBitrate             60000 Kbit/s
            ExpectedThroughput    31125 Kbit/s

Please note, that currently the router steers clients towards either 2.4 GHz
or 5 GHz. I already tried to restrict the client to either of both frequency
bands, but that did not seem to avoid the problem.

# uname -a
Linux mmm 6.0.0-2-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.0.5-1 (2022-10-28)
x86_64 GNU/Linux

(Probably) involved kernel modules:
rt2800usb rt2x00usb rt2800lib rt2x00lib mac80211 cfg80211

The device is a USB device
Ralink Technology, Corp. RT5572 Wireless Adapter

Any tips how to debug this?

From https://iwd.wiki.kernel.org/debugging I would assume, that IWD_GENL_DEBUG
might the relevant environment variable, but I am really not sure.
I could obviously implement some kind of watchdog checking the output of iwctl
every some seconds and restarting iwd in case, but I would avoid that if there
is a cleaner solution available.

I think is problem started to occur some months ago. It might be related with
some kernel or iwd update some time ago. But due to the long time until
occuring, a sound bisect might take more than a week.

Kind regards
Patrick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2022-11-06 14:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-06 14:36 Patrick Häcker [this message]
2022-11-07  3:46 ` Sometimes RxBitrate of 1000 Kbit/s Denis Kenzior
2022-11-10  3:18   ` Patrick Häcker
2022-11-10 15:27     ` Denis Kenzior

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5893463.lOV4Wx5bFT@mmm \
    --to=pat_h@web.de \
    --cc=iwd@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.