linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: David Mosberger <davidm@egauge.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: lost connectivity until "wpa_cli reassociate" is issued
Date: Thu, 7 Jan 2016 08:33:36 -0800	[thread overview]
Message-ID: <568E9360.3060906@candelatech.com> (raw)
In-Reply-To: <CALnQHM1mzqFbprQqujB7BWncOa=D9uAxLQ0paiv-21vrx+hFvw@mail.gmail.com>

On 01/07/2016 08:29 AM, David Mosberger wrote:
> Ben,
>
> On Thu, Jan 7, 2016 at 9:24 AM, Ben Greear <greearb@candelatech.com> wrote:
>> On 01/07/2016 08:19 AM, David Mosberger wrote:
>>>
>>> We are seeing a curious issue where WLAN connectivity sometimes
>>> gets stuck until a "wpa_cli reassociate" command is issued.
>>>
>>> At the WPA level, everything appears to be working fine)
>>> (see thread starting at
>>> http://lists.infradead.org/pipermail/hostap/2016-January/034454.html).
>>
>> I don't remember seeing you mention the driver and NIC you are using.
>>
>> I think this is likely a driver bug, so please provide that info.
>
> Sure, we're using rtl8192cu.  I started out suspecting a driver bug as
> well, but since we're processing management frames during those
> "stuck" periods just fine (see
> debug output in
> http://lists.infradead.org/pipermail/hostap/2016-January/034459.html),
> I'm not so sure anymore.  Like mac80211, we have patched rtl8192cu
> driver with current
> bug-fixes already.

I have no experience with that chip, but wifi is a tricky beast.  Could be
a power-save issue perhaps.  I assume you have sniffed to see if any frames
are going out on the air during the time of trouble?

If correct packets go out on the air and AP doesn't answer, then likely AP problem.

If pkts don't get on the air, then check to see if they at least get to
the driver.

If they don't get to the driver, then probably it is a kernel/stack issue.

If they get to the driver but not on the air, then NIC and/or it's firmware
and/or the driver is likely the culprit.

Thanks,
Ben

>
>    --david
>


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


  parent reply	other threads:[~2016-01-07 16:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-07 16:19 lost connectivity until "wpa_cli reassociate" is issued David Mosberger
2016-01-07 16:24 ` Ben Greear
2016-01-07 16:29   ` David Mosberger
2016-01-07 16:32     ` Krishna Chaitanya
2016-01-07 16:47       ` David Mosberger
2016-01-07 16:58         ` Krishna Chaitanya
2016-01-07 17:00           ` David Mosberger
2016-01-07 16:33     ` Ben Greear [this message]
2016-01-07 16:45       ` David Mosberger
2016-01-07 16:59     ` Bruno Randolf
2016-01-07 17:32       ` David Mosberger

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=568E9360.3060906@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=davidm@egauge.net \
    --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).