Bug 1251726

Summary: Hostapd fails to initialize 802.11 since update to kernel 2.6.32-573.1.1.el6.x86_64
Product: [Fedora] Fedora EPEL Reporter: Zebu1er <bugzilla.redhat.com>
Component: hostapdAssignee: John W. Linville <linville>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: el6CC: alex, cad73, daniel, g522k, linville, negativo17
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-10-12 10:28:38 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 Zebu1er 2015-08-09 09:08:54 UTC 
Description of problem:
The hostapd daemon fails to start because of an unexpected 80211 error.

Version-Release number of selected component (if applicable):
hostapd-2.0-7.el6.x86_64


How reproducible:
Booting with the last kernel 2.6.32-573.1.1.el6.x86_64 on Centos 6.7 will make hostapd to fail.
Booting with the previous kernel 2.6.32-504.30.3.el6.x86_64 will make it to work back again.


Steps to Reproduce:
1. Boot Centos 6.7 (x64) with new kernel 2.6.32-573.1.1.el6.x86_64
2. Start hostapd

Actual results:
The daemon fails to start, throwing the next message :
nl80211: Could not add multicast membership for scan events: -2 (No such file or directory)

Expected results:
The daemon starts without error and surrounding wifi devices see the AP

Additional info:

The command «locate 80211 | grep ko» gives the same driver list for both kernels.

The /etc/hostapd/hostapd.conf content :

ctrl_interface=/var/run/hostapd
ctrl_interface_group=wheel     
bridge=br0                                                                                       
interface=wlan0                                                                                  
hw_mode=g
channel=1
ssid=XXXXXXXXX
ignore_broadcast_ssid=2
auth_algs=1
macaddr_acl=0
wpa=3
wpa_key_mgmt=WPA-PSK
wpa_passphrase=XXXXXXXXXXXX
wpa_pairwise=TKIP
rsn_pairwise=CCMP
ieee80211n=1
driver=nl80211
wme_enabled=1
ht_capab=[HT20][HT40-][HT40+][SHORT-GI-20][SHORT-GI-40][RX-STBC1][DSSS_CCK-40][MAX-AMSDU-3839]
Comment 1 Zebu1er 2015-08-09 09:53:57 UTC 
The wireless driver is ath9k (AR9485, PCI VEN_168C/DEV_0032) which is loading correctly with both kernels.
Comment 2 Alexander Dalloz 2015-08-10 12:07:31 UTC 
Happens for me too. Rebooting with kernel 2.6.32-504.30.3.el6.x86_64 hostapd is lucky again.

hostapd-2.0-7.el6.x86_64

lspci -k
03:00.0 Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter (rev 01)
	Subsystem: Foxconn International, Inc. Device e052
	Kernel driver in use: ath9k
	Kernel modules: ath9k

/etc/hostapd/hostapd.conf
interface=wlan0
driver=nl80211
Comment 3 Zebu1er 2015-08-10 13:48:37 UTC 
Would be good to figure if only ath9k module users are affected...
Comment 4 groog 2015-08-15 13:21:03 UTC 
In addition to the epel package ,
https://w1.fi/hostapd/
The same can be compiled from the source code that you downloaded from
It confirmed the event .

In addition to the ath9 driver , use iwlwifi driver
also use the intel AC7260 was confirmed to be the same state .
Comment 5 groog 2015-08-15 13:24:43 UTC 
(In reply to groog from comment #4)
> In addition to the epel package ,
> https://w1.fi/hostapd/
> The same can be compiled from the source code that you downloaded from
> It confirmed the event .
> 
> In addition to the ath9 module , use iwlwifi module
> also use the intel AC7260 was confirmed to be the same state .
Comment 6 Davide A. Cardamone 2015-08-22 20:04:53 UTC 
Same issue for me too with a Ralink Technology, Corp. Conceptronic C300RU v2 802.11bgn Wireless Adapter [Ralink RT2770] .
Comment 7 Daniel Hokka Zakrisson 2015-09-03 17:01:28 UTC 
This is due to a bug in the kernel, see bug #1259870.
Comment 8 Zebu1er 2015-09-03 17:42:35 UTC 
(In reply to Daniel Hokka Zakrisson from comment #7)
> This is due to a bug in the kernel, see bug #1259870.

I can't see that bug (Access Denied - You are not authorized to access bug #1259870), I must lack particular privileges to do so...
Comment 9 Stanislaw Gruszka 2015-10-12 10:28:38 UTC 

*** This bug has been marked as a duplicate of bug 1259870 ***