Hostapd crashing

All,

since 18.06. I notice sporadic hostapd crashes.

Any ideas?


logread

Tue Mar 12 19:33:12 2019 daemon.warn hostapd: DFS failed to schedule CSA (-22) - trying fallback
Tue Mar 12 19:33:13 2019 kern.warn kernel: [1471750.078606] ------------[ cut here ]------------
Tue Mar 12 19:33:13 2019 kern.warn kernel: [1471750.083436] WARNING: CPU: 1 PID: 3341 at backports-2017-11-01/net/mac80211/ieee80211_i.h:1412 0xbf08108c [mac80211@bf07c000+0x5e000]
Tue Mar 12 19:33:13 2019 kern.warn kernel: [1471750.095584] Modules linked in: pppoe ppp_async pppox ppp_generic nf_conntrack_ipv6 iptable_nat ipt_REJECT ipt_MASQUERADE xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_FLOWOFFLOAD xt_CT slhc nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_conntrack_ipv4 nf_nat_ipv4 nf_nat nf_log_ipv4 nf_flow_table_hw nf_flow_table nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack iptable_mangle iptable_filter ip_tables crc_ccitt mwlwifi mac80211 cfg80211 compat ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables x_tables tun gpio_button_hotplug
Tue Mar 12 19:33:13 2019 kern.warn kernel: [1471750.155593] CPU: 1 PID: 3341 Comm: hostapd Not tainted 4.14.95 #0
Tue Mar 12 19:33:13 2019 kern.warn kernel: [1471750.161884] Hardware name: Marvell Armada 380/385 (Device Tree)
Tue Mar 12 19:33:13 2019 kern.warn kernel: [1471750.168004] Function entered at [<c010f144>] from [<c010ae30>]
Tue Mar 12 19:33:13 2019 kern.warn kernel: [1471750.174034] Function entered at [<c010ae30>] from [<c06245e8>]
Tue Mar 12 19:33:13 2019 kern.warn kernel: [1471750.180065] Function entered at [<c06245e8>] from [<c0121cdc>]
Tue Mar 12 19:33:13 2019 kern.warn kernel: [1471750.186095] Function entered at [<c0121cdc>] from [<c0121da8>]
Tue Mar 12 19:33:13 2019 kern.warn kernel: [1471750.192124] Function entered at [<c0121da8>] from [<bf08108c>]
Tue Mar 12 19:33:13 2019 kern.warn kernel: [1471750.198160] Function entered at [<bf08108c>] from [<bf097dd8>]
Tue Mar 12 19:33:13 2019 kern.warn kernel: [1471750.204191] Function entered at [<bf097dd8>] from [<bf05f5bc>]
Tue Mar 12 19:33:13 2019 kern.warn kernel: [1471750.210223] Function entered at [<bf05f5bc>] from [<c055a2a8>]
Tue Mar 12 19:33:13 2019 kern.warn kernel: [1471750.216253] Function entered at [<c055a2a8>] from [<c0559488>]
Tue Mar 12 19:33:13 2019 kern.warn kernel: [1471750.222283] Function entered at [<c0559488>] from [<c0559fb0>]
Tue Mar 12 19:33:13 2019 kern.warn kernel: [1471750.228312] Function entered at [<c0559fb0>] from [<c0558c5c>]
Tue Mar 12 19:33:13 2019 kern.warn kernel: [1471750.234341] Function entered at [<c0558c5c>] from [<c0559100>]
Tue Mar 12 19:33:13 2019 kern.warn kernel: [1471750.240371] Function entered at [<c0559100>] from [<c05087cc>]
Tue Mar 12 19:33:13 2019 kern.warn kernel: [1471750.246401] Function entered at [<c05087cc>] from [<c0508d00>]
Tue Mar 12 19:33:13 2019 kern.warn kernel: [1471750.252430] Function entered at [<c0508d00>] from [<c0509b00>]
Tue Mar 12 19:33:13 2019 kern.warn kernel: [1471750.258459] Function entered at [<c0509b00>] from [<c0107780>]
Tue Mar 12 19:33:13 2019 kern.warn kernel: [1471750.264496] ---[ end trace dcada47956e95aef ]---
Tue Mar 12 19:34:22 2019 daemon.err hostapd: Using interface wlan0 with hwaddr 5a:ef:68:xx:xx:xx and ssid "xxx"

---

head /etc/board.json
{
        "model": {
                "id": "armada-385-linksys-shelby",
                "name": "Linksys WRT1900ACS"
				...

---

uname -a
Linux front 4.14.95 #0 SMP Mon Jan 28 08:54:32 2019 armv7l GNU/Linux

---

cat /etc/os-release
NAME="OpenWrt"
VERSION="18.06.2"
ID="openwrt"
ID_LIKE="lede openwrt"
PRETTY_NAME="OpenWrt 18.06.2"
VERSION_ID="18.06.2"
HOME_URL="http://openwrt.org/"
BUG_URL="http://bugs.openwrt.org/"
SUPPORT_URL="http://forum.lede-project.org/"
BUILD_ID="r7676-cddd7b4c77"
LEDE_BOARD="mvebu/cortexa9"
LEDE_ARCH="arm_cortex-a9_vfpv3"
LEDE_TAINTS=""
LEDE_DEVICE_MANUFACTURER="OpenWrt"
LEDE_DEVICE_MANUFACTURER_URL="http://openwrt.org/"
LEDE_DEVICE_PRODUCT="Generic"
LEDE_DEVICE_REVISION="v0"
LEDE_RELEASE="OpenWrt 18.06.2 r7676-cddd7b4c77"

---

cat /etc/config/wireless

config wifi-device 'radio0'
        option type 'mac80211'
        option hwmode '11a'
        option path 'soc/soc:pcie/pci0000:00/0000:00:01.0/0000:01:00.0'
        option country 'DE'
        option legacy_rates '0'
        option channel '100'
        option htmode 'VHT40'

config wifi-iface 'default_radio0'
        option device 'radio0'
        option network 'lan'
        option mode 'ap'
        option macaddr '5a:ef:68:xx:xx:xx'
        option ssid 'xxx'
        option encryption 'psk2+ccmp'
        option key 'xxx'

config wifi-device 'radio1'
        option type 'mac80211'
        option hwmode '11g'
        option path 'soc/soc:pcie/pci0000:00/0000:00:02.0/0000:02:00.0'
        option htmode 'HT20'
        option country 'DE'
        option legacy_rates '1'
        option channel '13'
        option txpower '20'

config wifi-iface 'default_radio1'
        option device 'radio1'
        option network 'lan'
        option mode 'ap'
        option macaddr '5a:ef:68:xx:xx:xx'
        option ssid 'yyy'
        option encryption 'psk2+ccmp'
        option key 'yyy'

---

Don't use DFS channels (5GHz Ch. 52-64 & 100-140) on mwlwifi devices (Linksys WRT AC series etc.). It varies from device to device and region to region but from what I've gathered in the WiFi driver repository, EU devices generally have more issues with DFS on mwlwifi. Don't have hope in this being fixed in the future. The driver developer (a single Marvell employee) has stopped all work on trying to further stabilize DFS (on anything other than a 3200ACM) and is now working on 802.11ax.

TL;DR: Change the 5GHz wifi channel from 100 on your 1900ACS to anything in between 36-48 (149-165 is sadly unavailable in the EU).

@3DIRK Please use "Preformatted text </>" for logs, scripts, configs and general console output.
Please edit your posting accordingly.

No errors since then. Thx, @ParanoidZoid

Issue solved.

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.