Bug 881342

Summary:	ath9k error: Device or resource busy (-16)
Product:	[Fedora] Fedora	Reporter:	nucleo <alekcejk>
Component:	aircrack-ng	Assignee:	Till Maas <opensource>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	17	CC:	blaffablaffa, gansalmon, itamar, jonathan, kernel-maint, lmacken, madhu.chinakonda, opensource
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-04-17 00:20:24 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description nucleo 2012-11-28 18:27:08 UTC

Description of problem:
After updating kernel from 3.5.6 to 3.6.x there are errors in kismet_server and airmon-zc commands.

Version-Release number of selected component (if applicable):
kernel-3.6.8-2.fc17.i686

How reproducible:
Every time.

Steps to Reproduce:
1. run kismet_server as root (previously setup /etc/kismet/kismet.conf)
2. or run "airmon-zc start wlan0 9"
3.
  
Actual results:
Error in kismet_server:
ERROR: mac80211_setchannel() could not set channel 1/2412 on interface 'wlan0mon' err -16

Error in airmon-zc:
K[phy0]wlan0    ath9k[mac80211]-N/A    Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)  command failed: Device or resource busy (-16)


Expected results:
Should not be error messages.

Additional info:
Last kernel without such errors is kernel-3.5.7-1.fc16.i686.
Updating iw to iw-3.7-1.fc18.i686 don't solved problem.

Comment 1 nucleo 2012-11-28 18:29:02 UTC

Note that wlan0 is definitely not connected to access point.
Command also fails even if I stop NetworkManager and wpa_supplicant services.

Comment 2 Lorenzo Pistone 2012-11-28 19:29:54 UTC

Same problem with Intel Ultimate N WiFi Link 5300 (iwlwifi). I have to conclude that the problem is in mac80211 or cfg80211.

Simple command to reproduce the issue:
iw dev wlan0 set channel 7

Comment 3 nucleo 2012-12-04 00:37:56 UTC

Bug still present with kernel-3.6.9-1.fc17.i686.

Comment 4 Lorenzo Pistone 2012-12-04 11:40:11 UTC

After a talk in #linux-wireless, I understood the cause.
It's something about channel contexts that have been merged among interfaces, so basically wlan0 is holding a lock on channel switch. If you bring down wlan0 ('ifconfig wlan0 down' or 'ip' equivalent), you will be able to switch channel again. Since we weren't able (righteously) to change channel when wlan0 was up and attached to an AP, then this new behaviour doesn't really change or prevent anything, and on the other hand it's safer (you must bring down what expects to have full control on channel switches before handling them manually). So I'd say that it's not a bug.

Comment 5 nucleo 2012-12-04 13:25:56 UTC

'ifconfig wlan0 down' can't fix problem because when kismet_server running wlan0 state again changed to UP, so -16 error appears again. The same problem with airmon-zc.

Comment 6 Lorenzo Pistone 2012-12-04 17:16:09 UTC

first run airmon-zc with wlan0, then bring wlan0 down. That's what I do. Also, the airmon-ng developers are aware of this issue, and I think they will adapt the script.
I don't know kismet, so I can't help you, but that's for sure something on kismet side. I still think that this is not a bug.

Comment 7 nucleo 2013-03-01 22:15:26 UTC

Any news here?
Should kismet and aircrack-ng fixed or kernel?

Comment 8 nucleo 2013-03-14 03:58:10 UTC

kismet bug 917276 fixed, so now only aircrack-ng needs to be fixed.

Comment 9 nucleo 2013-03-14 16:06:26 UTC

This error fixed in aircrack-ng svn, so building new snapshot should fix this bug.

r2237 | Zero_Chaos | 2013-01-30 01:59:27 +0200 (Ср., 30 янв. 2013) | 2 lines
airmon-zc: fix error 16 when starting monitor mode

Comment 10 Fedora Update System 2013-04-08 08:36:39 UTC

aircrack-ng-1.1-7.20130402svn.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/aircrack-ng-1.1-7.20130402svn.fc18

Comment 11 Fedora Update System 2013-04-08 08:36:51 UTC

aircrack-ng-1.1-7.20130402svn.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/aircrack-ng-1.1-7.20130402svn.fc17

Comment 12 Fedora Update System 2013-04-08 08:37:01 UTC

aircrack-ng-1.1-7.20130402svn.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/aircrack-ng-1.1-7.20130402svn.fc19

Comment 13 Fedora Update System 2013-04-08 15:47:07 UTC

Package aircrack-ng-1.1-7.20130402svn.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing aircrack-ng-1.1-7.20130402svn.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-5113/aircrack-ng-1.1-7.20130402svn.fc19
then log in and leave karma (feedback).

Comment 14 Fedora Update System 2013-04-17 00:20:26 UTC

aircrack-ng-1.1-7.20130402svn.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 15 Fedora Update System 2013-04-17 00:20:48 UTC

aircrack-ng-1.1-7.20130402svn.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 16 Fedora Update System 2013-04-20 19:22:14 UTC

aircrack-ng-1.1-7.20130402svn.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.