On 23-3-2016 20:13, Rafał Miłecki wrote: > On 23 March 2016 at 11:44, Arend Van Spriel > <arend.vanspriel@xxxxxxxxxxxx> wrote: >> On 23-3-2016 9:47, Rafał Miłecki wrote: >>> On 22 March 2016 at 21:24, Arend van Spriel >>> <arend.vanspriel@xxxxxxxxxxxx> wrote: >>>> On 22-3-2016 7:36, Rafał Miłecki wrote: >>>>> Hi, any ideas / help regarding this issue? >>>> >>>> Restarting hostapd obviously is a valid scenario. My guess is >>>> we would need to avoid interface removal in >>>> brcmf_notify_connect_status_ap. But first I would like to know >>>> in which state the firmware is upon brcmf_ap_add_vif. Can you >>>> provide a full log with FWCON debug level enabled? >>> >>> Sure, hope it helps! >> >> Ah. Actually would like to see some driver logging as well so >> 'debug=0x101410'. > > Sure, there you go. A bit overdue, but here we go. Upon killing hostapd it results in brcmf_cfg80211_stop_ap() for 'OpenWrt5x' bss and we give a DOWN command for the interface to firmware. However, we get a link down for the primary interface *and* second interface. [ 172.799334] brcmfmac: brcmf_fil_cmd_int_set ifidx=1, cmd=3, value=1 [ 172.802111] brcmfmac: CONSOLE: 026767.523 wl0: link down (wl0) [ 172.802147] brcmfmac: CONSOLE: 026767.523 wl0: link down (wl0.2) [ 172.802166] brcmfmac: brcmf_fweh_event_worker event LINK (16) ifidx 0 bsscfg 0 addr 90:8d:78:66:3a:56 [ 172.802173] brcmfmac: brcmf_fweh_event_worker version 2 flags 0 status 0 reason 4 [ 172.802178] brcmutil: event payload, len=0 [ 172.802202] brcmfmac: brcmf_fweh_event_worker event LINK (16) ifidx 1 bsscfg 2 addr 92:8d:78:66:3a:57 [ 172.802208] brcmfmac: brcmf_fweh_event_worker version 2 flags 0 status 0 reason 4 [ 172.802212] brcmutil: event payload, len=0 Looking into the firmware code it turns out that the DOWN command brings down the entire stack iso single interface. This seems specific for some firmware branches so we have to find a better solution. Hante and I are looking into it. Regards, Arend -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
