From: Johannes Berg <johannes@sipsolutions.net>
To: Dennis New <dennisn@dennisn.mooo.com>, linux-wireless@vger.kernel.org
Subject: Re: wlan0 keeps deauthenticating DEAUTH_LEAVING about every minute
Date: Wed, 29 Mar 2017 09:34:50 +0200 [thread overview]
Message-ID: <1490772890.18052.8.camel@sipsolutions.net> (raw)
In-Reply-To: <20170324213237.6f122a9173fa464a5d936f9d@dennisn.mooo.com> (sfid-20170325_024055_755712_8E7A9C9D)
On Fri, 2017-03-24 at 21:32 -0400, Dennis New wrote:
> Ever since I upgraded to the 4.10 kernels (I don't think this
> behavior existed in the 4.8 series), after I startup my laptop
> (either from cold boot, or from standby), my wlan0 interface keeps
> deauthenticating
> ...
> 19:23:29 kernel: wlan0: authenticate with 00:11:22:33:44:55
> 19:23:29 kernel: ------------[ cut here ]------------
> 19:23:29 kernel: WARNING: CPU: 0 PID: 18925 at
> net/mac80211/mlme.c:287 ieee80211_determine_chantype+0x12e/0x380
This is already indicating a severe problem. I don't know how you end
up in this situation with b43, since that doesn't have any regulatory
magic afaict.
> 19:23:29 kernel: wlan0: associated
>
> 19:24:29 kernel: wlan0: deauthenticating from 00:11:22:33:44:55 by
> local choice (Reason: 3=DEAUTH_LEAVING)
>
I'm convinced that this comes from reg_check_channels().
The above WARN_ON() already told you that the channel was considered
invalid.
Do you know what channel your AP is on? Perhaps show the output of "iw
wlan0 scan dump" while it's connected (you have 60 seconds :P)
Can you please show the output of "iw list" and "iw phy0 channels"?
johannes
next prev parent reply other threads:[~2017-03-29 7:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-25 1:32 wlan0 keeps deauthenticating DEAUTH_LEAVING about every minute Dennis New
2017-03-26 16:00 ` Larry Finger
2017-03-26 17:43 ` Dennis New
2017-03-26 18:47 ` Arend Van Spriel
2017-03-26 18:51 ` Dennis New
2017-03-26 19:00 ` Arend Van Spriel
2017-03-29 7:34 ` Johannes Berg [this message]
2017-03-29 7:43 ` Arend Van Spriel
2017-03-29 7:46 ` Johannes Berg
2017-03-29 8:20 ` Arend Van Spriel
2017-03-29 8:50 ` Johannes Berg
2017-03-29 10:28 ` Dennis New
2017-03-29 11:49 ` Johannes Berg
2017-03-29 18:58 ` Arend Van Spriel
2017-03-30 8:06 ` Johannes Berg
2017-03-29 19:36 ` Dennis New
2017-03-29 20:15 ` Larry Finger
2017-03-29 20:21 ` Arend Van Spriel
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=1490772890.18052.8.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=dennisn@dennisn.mooo.com \
--cc=linux-wireless@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).