linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: 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 09:57:45 -0600	[thread overview]
Message-ID: <53189AF9.9030707@lwfinger.net> (raw)
In-Reply-To: <531777F8.5060506@connotech.com>

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 have no idea why that particular set of commands fails to be able to set the 
channel. Both NetworkManager and the openSUSE ifup sequence work OK. Your system 
can set channels using the scan mechanism.

If you want to track it down, you will need to put printk statements at every 
place that the net/wireless code sets EBUSY to see which one triggers. Perhaps 
that will expose any bug there, or in your script.

Larry



  parent reply	other threads:[~2014-03-06 15:57 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 [this message]
2014-03-06 17:40           ` Dan Williams
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=53189AF9.9030707@lwfinger.net \
    --to=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 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).