All of lore.kernel.org
 help / color / mirror / Atom feed
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 13:49:06 +0200	[thread overview]
Message-ID: <1490788146.7948.19.camel@sipsolutions.net> (raw)
In-Reply-To: <20170329062808.032e71a5327f3405f82df4b2@dennisn.mooo.com> (sfid-20170329_122846_570548_1B99027C)

On Wed, 2017-03-29 at 06:28 -0400, Dennis New wrote:
> On Wed, 29 Mar 2017 09:34:50 +0200, Johannes Berg wrote:
> > 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?
> 
> 6
> 
> > Perhaps show the output of "iw wlan0 scan dump" while it's
> 
> connected (you have 60 seconds :P)
> 
> I have been having stable connections for the past few days,
> simply by putting a 60 second sleep before starting my wlan0.
> Although
> if I /etc/init.d/net.wlan0 restart it (without the delay), it will
> still do this deauth'ing.

Very strange.

> 	* 2437 MHz [6] 
> 	  Maximum TX power: 20.0 dBm
> 	  Channel widths:

That's quite odd, why isn't it listing any possible channel widths?!

I get:
	* 2437 MHz [6] 
	  Maximum TX power: 15.0 dBm
	  Channel widths: 20MHz HT40- HT40+

What's "iw reg get"?

johannes

  reply	other threads:[~2017-03-29 11:49 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
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 [this message]
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=1490788146.7948.19.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.