From: Jouni Malinen <jouni@qca.qualcomm.com>
To: Daniel Drake <drake@endlessm.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
ath9k-devel <ath9k-devel@qca.qualcomm.com>,
Linux Upstreaming Team <linux@endlessm.com>
Subject: Re: ath9k disconnects in 4.13 with reason=4 locally_generated=1
Date: Fri, 3 Nov 2017 09:51:19 +0000 [thread overview]
Message-ID: <20171103095112.GA14915@jouni.qca.qualcomm.com> (raw)
In-Reply-To: <CAD8Lp47N8ENCPp0ELd5_H8efEna9FGemM-vvi0kf7=coG5tNXA@mail.gmail.com>
On Fri, Nov 03, 2017 at 10:57:11AM +0800, Daniel Drake wrote:
> Endless OS recently upgraded from Linux 4.11 to Linux 4.13, and we now
> have a few reports of issues with ath9k wireless becoming unusable.
>=20
> In the logs we can see that it authenticates, associates and completes
> the WPA 4 way handshake, before then being disconnected with:
>=20
> wlp2s0: CTRL-EVENT-DISCONNECTED bssid=3D74:26:ac:68:2f:c0 reason=3D4
> locally_generated=3D1
reason=3D4 is WLAN_REASON_DISASSOC_DUE_TO_INACTIVITY. I'd expect the most
likely source of this to be one of the mac80211 code paths in mlme.c
where disconnection is triggered if the current AP become unreachable.
Getting a debug log from mac80211 might help in figuring out what is
causing this (there seem to be number of mlme_dbg() calls before most,
but not necessarily all, places where
WLAN_REASON_DISASSOC_DUE_TO_INACTIVITY is used).
--=20
Jouni Malinen PGP id EFC895FA=
next prev parent reply other threads:[~2017-11-03 9:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 2:57 ath9k disconnects in 4.13 with reason=4 locally_generated=1 Daniel Drake
2017-11-03 9:51 ` Jouni Malinen [this message]
2017-11-10 1:30 ` Daniel Drake
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=20171103095112.GA14915@jouni.qca.qualcomm.com \
--to=jouni@qca.qualcomm.com \
--cc=ath9k-devel@qca.qualcomm.com \
--cc=drake@endlessm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@endlessm.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