From: Kalle Valo <kvalo@kernel.org>
To: Dennis Baurichter <dennisba@mail.uni-paderborn.de>
Cc: Zachary Michaels <mikezackles@gmail.com>,
linux-wireless@vger.kernel.org, Troy Volin <tmvolin@gmail.com>,
Gregory Greenman <gregory.greenman@intel.com>
Subject: Re: [PATCH] iwlwifi: Make missed beacon timeout configurable
Date: Wed, 03 Aug 2022 07:32:13 +0300 [thread overview]
Message-ID: <871qtyj6b6.fsf@kernel.org> (raw)
In-Reply-To: <c09a353b-8e52-6d9d-a3c6-743e4e6f444b@mail.uni-paderborn.de> (Dennis Baurichter's message of "Tue, 2 Aug 2022 20:50:31 +0200")
Dennis Baurichter <dennisba@mail.uni-paderborn.de> writes:
> Hello,
>
> the below patch was sent to linux-wireless 5 months ago, but (as far
> as I can see on lore.kernel.org) didn't get a reply, so I guess it
> might have slipped through? May I ask to consider it for inclusion?
>
> As stated below, this is a workaround for frequent wifi disconnects
> described in https://bugzilla.kernel.org/show_bug.cgi?id=203709. As an
> example, on one laptop with Intel Dual Band Wireless AC 3160 these
> disconnects occured sporadically initially, but later became very
> frequent, e.g. around 100 disconnects within 5 hours (with the laptop
> 1m from the wifi access point). Setting the beacon_timeout parameter
> provided by the patch allowed me to completely "fix" / work around the
> problem, with no disconnects anymore. Many more examples can be found
> in the linked bug report.
The patch did get to patchwork and is assigned to Gregory:
https://patchwork.kernel.org/project/linux-wireless/patch/20220226045047.643695-1-mikezackles@gmail.com/
Gregory, please take a look. This looks to be a common problem.
Not really fond of a module parameter approach, I think it should be
automatic. Why not just increase the default beacon timeout value?
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-08-03 4:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-26 4:50 [PATCH] iwlwifi: Make missed beacon timeout configurable Zachary Michaels
2022-08-02 18:50 ` Dennis Baurichter
2022-08-03 4:32 ` Kalle Valo [this message]
2022-08-03 15:50 ` Zachary Michaels
2022-08-14 13:05 ` Greenman, Gregory
2022-08-14 16:01 ` Zachary Michaels
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=871qtyj6b6.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=dennisba@mail.uni-paderborn.de \
--cc=gregory.greenman@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mikezackles@gmail.com \
--cc=tmvolin@gmail.com \
/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