From: Larry Finger <Larry.Finger@lwfinger.net>
To: Mike Turner <miketurner.forum@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: rtl8192cu beacon fix unreliable
Date: Wed, 18 Feb 2015 15:27:12 -0600 [thread overview]
Message-ID: <54E503B0.8020904@lwfinger.net> (raw)
In-Reply-To: <loom.20150213T114021-973@post.gmane.org>
On 02/13/2015 04:48 AM, Mike Turner wrote:
> When using hostapd and an rtl8192cu Wireless USB adaptor the beacon
> doesn't start sometimes. This was tested with the
>
> kernel/git/davem/net-next.git repository
>
> and
>
> 3423eb92315865d76cb8d488513bfef6ab9251d0
>
> This behaviour is apparently random. If the beacon starts OK then it
> continues. If a beacon isn't generated then it never starts. Repeating
> cycles of hostapd stop/start may or may not generate a beacon. There are
> no specific error messages displayed either on console or in syslog. I
> have repeated hostapd stop/start a number of consecutive times and
> received a beacon each time, however I have also done this a number of
> times and never generated a beacon.
>
> We have succesfully used the pvaret-rtl8192cu driver which is based on the
> vendor driver and used that in conjunction with the modified hostapd code
> that requires use of the rtl871xdrv driver interface and as far as we have
> seen it always generates a beacon.
>
> Platform is a custom designed Atmel-ARM CPU (AT91SAM9G25) with a D-Link
> DWA-121.
Is send_beacon_frame() being called even when the beacon fails to start? Adding
a pr_info() at the start of the routine should answer that question.
Larry
next prev parent reply other threads:[~2015-02-18 21:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-13 10:48 rtl8192cu beacon fix unreliable Mike Turner
2015-02-18 21:27 ` Larry Finger [this message]
[not found] ` <CALA4C6XecJ+zGGfWkO51red7S-2mNoVC6vkD0ama1AGat2QOHg@mail.gmail.com>
2015-02-19 18:19 ` Larry Finger
2015-02-20 11:44 ` Mike Turner
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=54E503B0.8020904@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=miketurner.forum@gmail.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;
as well as URLs for NNTP newsgroup(s).