On Sun, Aug 14, 2022 at 6:05 AM Greenman, Gregory <gregory.greenman@xxxxxxxxx> wrote: > > On Wed, 2022-08-03 at 08:50 -0700, Zachary Michaels wrote: > > > Why not just increase the default beacon timeout value? > > > > I made it a parameter because I was under the vague impression that a > > larger timeout wouldn't be ideal on a well-behaved network, but this > > isn't my area of expertise. I just thought this would be the most > > conservative change since it would support identical default > > operation. > > > > Thanks for taking a look. > > I see that this issue https://bugzilla.kernel.org/show_bug.cgi?id=203709 > has a long history from 2019. But, anyway, what value for > beacon_timeout solves the problem? It seems that most people have had success with 256, but that number may be somewhat arbitrary. > May I ask you to perform two experiments that could help us find > the root cause for this issue? The first is to run with a default driver and > to collect a firmware dump (here is a wiki with directions how to do that, > https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging#firmware_debugging) > and the second is to load the defaut driver with modparam power_scheme=1. This will > completely disable power save and will let us know if the issue is somehow caused by > the NIC going to sleep and missing beacons. > > Thanks, > Gregory Unfortunately I am no longer experiencing this issue, but someone else on this chain may be able to help. (Someone having problems requested that I submit the patch.) There may be some relevant information in the linked bug report if you care to sift through it. There are reports that turning off power save did not work, and there are also some firmware dumps. Best, -Zach
