From: Dan Williams <dcbw@redhat.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Thierry Moreau <thierry.moreau@connotech.com>,
linux-wireless@vger.kernel.org
Subject: Re: rtlwifi (rtl8192ce) consistently reports EBUSY error, but scanning works
Date: Thu, 06 Mar 2014 11:40:43 -0600 [thread overview]
Message-ID: <1394127643.10175.13.camel@dcbw.local> (raw)
In-Reply-To: <53189AF9.9030707@lwfinger.net>
On Thu, 2014-03-06 at 09:57 -0600, Larry Finger wrote:
> On 03/05/2014 01:16 PM, Thierry Moreau wrote:
> > On 03/05/14 16:40, Larry Finger wrote:
> >>
> >> Please give me the exact set of commands you use to get this problem. If
> >> possible, capture the console output. As I am currently running
> >> long-term tests of the latest version of rtl8192ce using an RTL8188CE
> >> (10ec:8176), it will be a perfect time to test.
> >>
> >
> > Here is the command script, and the console log
> > (....sh 2>&1 | tee ....log)
> >
> > Is it possible that the Shuttle system be arranged with a digital output
> > enabling/inhibiting the Realtek wifi interface active participation in wifi
> > protocol?
> >
> > I did ask Shuttle tech support, but in any event I don't want to induce you to
> > troubleshoot a specific system.
>
> The problem is not specific to the Shuttle - I can reproduce it on my HP laptop.
> Furthermore, it affects other mac80211-based drivers. The EBUSY return comes out
> of mac80211/cfg80211/nl80211 code.
I deleted the earlier bits of this thread after skimming it, but IIRC
we're talking about scanning here right? If there's already a scan
in-progress, then the stack can often return EBUSY.
For example, from both cfg80211_wext_siwscan() and
nl80211_trigger_scan(), used by 'iwlist' and 'iw' respectively:
if (rdev->scan_req) {
err = -EBUSY;
goto out;
}
Scans do not get canceled just because another random scan request comes
in. Whatever userspace there is needs to wait for a scan completion
event and then request it's new scan. There are also stack internal
scans that happen from time to time that may cause a user-requested scan
to return EBUSY.
(NM hands this all off to wpa_supplicant, which itself handles the EBUSY
by waiting a bit and then requesting another scan.)
Dan
next prev parent reply other threads:[~2014-03-06 17:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 6:36 rtlwifi (rtl8192ce) consistently reports EBUSY error, but scanning works Thierry Moreau
2014-03-05 7:12 ` Larry Finger
2014-03-05 16:27 ` Thierry Moreau
2014-03-05 16:40 ` Larry Finger
2014-03-05 19:16 ` Thierry Moreau
2014-03-06 14:54 ` Peter Wu
2014-03-06 18:59 ` Thierry Moreau
2014-03-06 15:57 ` Larry Finger
2014-03-06 17:40 ` Dan Williams [this message]
2014-03-05 10:51 ` Peter Wu
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=1394127643.10175.13.camel@dcbw.local \
--to=dcbw@redhat.com \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=thierry.moreau@connotech.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 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.