From: "Patrick Häcker" <pat_h@web.de>
To: iwd@lists.linux.dev, Denis Kenzior <denkenz@gmail.com>
Subject: Re: Sometimes RxBitrate of 1000 Kbit/s
Date: Thu, 10 Nov 2022 04:18:14 +0100 [thread overview]
Message-ID: <2259038.ElGaqSPkdT@mmm> (raw)
In-Reply-To: <4d50da71-40e3-f888-be79-b52fa8208e88@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1330 bytes --]
Hi Denis,
> iwd doesn't do anything on sleep (it isn't even aware of sleep). So it is
> up to the kernel driver to do the right thing. Maybe it isn't? You'll
> have to ask the kernel / driver / firmware people for your hardware.
thanks a lot for the answer. I'll contact the kernel / driver / firmware people
for my hardware.
> Some network managers (like NM) will explicitly IFDOWN wireless interfaces
> on suspend and bring them up on resume. This isn't cost free and we'd
> rather not do this.
Would it make sense to do this optionally if a new config option were
explicitly set? Or do you think this is the wrong layer or wrong approach to
do so?
> You can also try to run run iwmon in order to capture what is happening on
> the nl80211 API level when entering / leaving suspend. The driver people
> might be interested in this information.
I was monitoring with iwmon for the last days whenever the computer was in
use, but so far the problem did not occur again (it occurs during normal
operation, I just have the feeling that the probability is highest some
minutes after waking up from suspend).
The only thing I got was a segfault from iwmon once, so it's now running with
valgrind. This is, however, probably an unrelated issue, if it should repeat
at all.
Thanks again
Patrick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-11-10 3:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-06 14:36 Sometimes RxBitrate of 1000 Kbit/s Patrick Häcker
2022-11-07 3:46 ` Denis Kenzior
2022-11-10 3:18 ` Patrick Häcker [this message]
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=2259038.ElGaqSPkdT@mmm \
--to=pat_h@web.de \
--cc=denkenz@gmail.com \
--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.