From: Arend Van Spriel <arend.vanspriel@broadcom.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: brcm80211 development <brcm80211-dev-list@broadcom.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Brett Rudley <brudley@broadcom.com>,
Arend van Spriel <arend@broadcom.com>,
"Franky (Zhenhui) Lin" <frankyl@broadcom.com>,
Hante Meuleman <meuleman@broadcom.com>
Subject: Re: Problem with brcmfmac removing extra interface
Date: Tue, 24 May 2016 21:49:36 +0200 [thread overview]
Message-ID: <590f02bf-63a1-9510-dddb-d903fe03284e@broadcom.com> (raw)
In-Reply-To: <CACna6rwrNWzU415zK43fiwBc+BbfosdiSrJk11=pCs7uZDYV=w@mail.gmail.com>
On 23-3-2016 20:13, Rafał Miłecki wrote:
> On 23 March 2016 at 11:44, Arend Van Spriel
> <arend.vanspriel@broadcom.com> wrote:
>> On 23-3-2016 9:47, Rafał Miłecki wrote:
>>> On 22 March 2016 at 21:24, Arend van Spriel
>>> <arend.vanspriel@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.
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
next prev parent reply other threads:[~2016-05-24 19:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 22:37 Problem with brcmfmac removing extra interface Rafał Miłecki
2016-03-22 6:36 ` Rafał Miłecki
2016-03-22 20:24 ` Arend van Spriel
2016-03-23 8:47 ` Rafał Miłecki
2016-03-23 10:44 ` Arend Van Spriel
2016-03-23 19:13 ` Rafał Miłecki
2016-05-06 22:43 ` Rafał Miłecki
2016-05-24 19:49 ` Arend Van Spriel [this message]
2016-05-25 7:56 ` Rafał Miłecki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=590f02bf-63a1-9510-dddb-d903fe03284e@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=arend@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=brudley@broadcom.com \
--cc=frankyl@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=meuleman@broadcom.com \
--cc=zajec5@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).