linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Cannot set frequency on phy device in 3.9.0+ ??
Date: Tue, 07 May 2013 10:02:22 -0700	[thread overview]
Message-ID: <5189339E.7090502@candelatech.com> (raw)

Seems like this used to work.  NIC is ath9k_htc driver, configured with one
VAP and one station.  Both are admin down, but still get EBUSY when trying
to set the frequency.  Seems like this used to work (on ath9k driver, at least).

[root@lec2010-ath9k-1 lanforge]# ifconfig wlan1
wlan1     Link encap:Ethernet  HWaddr A0:F3:C1:24:61:2B
           inet addr:11.97.2.5  Bcast:11.97.255.255  Mask:255.255.0.0
           BROADCAST MULTICAST  MTU:1500  Metric:1
           RX packets:761 errors:0 dropped:0 overruns:0 frame:0
           TX packets:402 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:129222 (126.1 KiB)  TX bytes:74364 (72.6 KiB)

[root@lec2010-ath9k-1 lanforge]# ifconfig vap1
vap1      Link encap:Ethernet  HWaddr 00:A0:00:00:00:90
           inet addr:10.99.1.1  Bcast:10.99.255.255  Mask:255.255.0.0
           BROADCAST MULTICAST  MTU:1500  Metric:1
           RX packets:16435018 errors:0 dropped:0 overruns:0 frame:0
           TX packets:9082445 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:2204413501 (2.0 GiB)  TX bytes:1451899217 (1.3 GiB)

[root@lec2010-ath9k-1 lanforge]# ./local/sbin/iw phy wiphy1 set freq 2437
command failed: Device or resource busy (-16)

Thanks,
Ben

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


                 reply	other threads:[~2013-05-07 17:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=5189339E.7090502@candelatech.com \
    --to=greearb@candelatech.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 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).