On 23 March 2016 at 20:13, Rafał Miłecki <zaj...@gmail.com> wrote: > On 23 March 2016 at 11:44, Arend Van Spriel > <arend.vanspr...@broadcom.com> wrote: >> On 23-3-2016 9:47, Rafał Miłecki wrote: >>> On 22 March 2016 at 21:24, Arend van Spriel >>> <arend.vanspr...@broadcom.com> 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.
Did this allow you to understand this problem any better? Do you have any idea for a solution? -- Rafał -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
