From: James Prestwood <prestwoj@gmail.com>
To: "Johnson, Bryce" <Bryce.Johnson@landisgyr.com>,
"iwd@lists.linux.dev" <iwd@lists.linux.dev>
Subject: Re: wiphy_estimate_data_rate() failed
Date: Wed, 21 Sep 2022 13:43:29 -0700 [thread overview]
Message-ID: <77f95956dde70bfa43376b9e36430f5a14c71ee4.camel@gmail.com> (raw)
In-Reply-To: <AS8PR01MB74931FD1507D2D70FDFB5F05F44F9@AS8PR01MB7493.eurprd01.prod.exchangelabs.com>
On Wed, 2022-09-21 at 20:04 +0000, Johnson, Bryce wrote:
> Hi all,
> I recently updated to use IWD 1.30. I also recently added a script
> to call `iwctl station wlan0 scan` and then `iwctl station wlan0 get-
> networks rssi-dbms` to write out to a log file every minute for
> debugging. When I went to check my iwd log I noticed it was filled
> up with wiphy_estimate_data_rate() failed errors.
This isn't a fatal error, just a warning. It means IWD couldn't parse
either HE/VHT/HT or basic rates from the scan results. This just means
that BSS gets a very low rank.
>
> I stopped my scan script and manually called `iwctl station wlan0
> scan` and was able to cause the error. I did also get a deauth
> event around that time when I was looking at it, but not sure what
> caused that.
>
> Received Deauthentication event, reason: 4, from_ap: false
The above warning definitely won't cause a disconnect.
>
>
> I restarted my device, but I haven't seen the problem happen again.
> I was going to start IWD in debug mode to get more information.
> Anything else to capture if I see the issue?
It is probably a network around you that isn't yours and IWD's quick
scan isn't seeing it. You'll probably see it if you do a full scan
again.
>
> Thanks
> Bryce
>
next prev parent reply other threads:[~2022-09-21 20:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 20:04 wiphy_estimate_data_rate() failed Johnson, Bryce
2022-09-21 20:43 ` James Prestwood [this message]
2022-09-21 21:08 ` Johnson, Bryce
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=77f95956dde70bfa43376b9e36430f5a14c71ee4.camel@gmail.com \
--to=prestwoj@gmail.com \
--cc=Bryce.Johnson@landisgyr.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox