CHROMIUMOS: mac80211: Set beacon loss detection parameters to be more lenient

This is a workaround to reduce the impact of bug 4886 while we
attempt to get a proper fix in.  This will allow us to cling to
the AP a bit longer while the receiver is stuck.

Signed-off-by: Paul Stewart <pstew@chromium.org>
BUG=chrome-os-partner:4886
TEST=TEST=Manual: Bench-top re-enactment of congested environment +
in-field testing with client machines

Change-Id: I92d5f405287787ee75a78644de36c33b53685a10
Reviewed-on: https://gerrit.chromium.org/gerrit/15862
Reviewed-by: Sam Leffler <sleffler@chromium.org>
Tested-by: Paul Stewart <pstew@chromium.org>
Commit-Ready: Paul Stewart <pstew@chromium.org>

diff --git a/net/mac80211/mlme.c b/net/mac80211/mlme.c
index 20c680b..0f15d7d 100644 (file)
--- a/net/mac80211/mlme.c
+++ b/net/mac80211/mlme.c
@@ -36,7 +36,7 @@
 #define IEEE80211_ASSOC_TIMEOUT (HZ / 5)
 #define IEEE80211_ASSOC_MAX_TRIES 3
 
-static int max_nullfunc_tries = 2;
+static int max_nullfunc_tries = 10;
 module_param(max_nullfunc_tries, int, 0644);
 MODULE_PARM_DESC(max_nullfunc_tries,
                 "Maximum nullfunc tx tries before disconnecting (reason 4).");
@@ -54,7 +54,7 @@ MODULE_PARM_DESC(max_probe_tries,
  * probe on beacon miss before declaring the connection lost
  * default to what we want.
  */
-#define IEEE80211_BEACON_LOSS_COUNT    7
+#define IEEE80211_BEACON_LOSS_COUNT    14
 
 /*
  * Time the connection can be idle before we probe