From: Ferry Toth <fntoth@gmail.com>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>
Cc: linux-wireless@vger.kernel.org, brcm80211@lists.linux.dev,
brcm80211-dev-list.pdl@broadcom.com,
linux-kernel@vger.kernel.org
Subject: brcmfmac: Can not completely turn off AP (BCM43340/2)
Date: Sat, 19 Jul 2025 22:57:24 +0200 [thread overview]
Message-ID: <dc05e447-06a1-4865-8252-c4a0710d6da9@gmail.com> (raw)
In-Reply-To: <20250407042028.1481-1-vulab@iscas.ac.cn>
Hi,
I have an Intel Edison board with BCM43340/2.
I am currently running 6.12.39-edison-acpi-preempt-rt which is mostly
mainline with a Yocto 5.0.11 (scarthgap) user space.
When I turn on tethering (using connman) it seems to be working fine.
But when I turn off tethering, connman seems to be believe it is off,
but I can still see the AP with my phone.
After this wifi is dead (can not scan, connect, tether on again,
nothing) and connman believes wifi is not supported. The only way to get
it working after this is reboot.
While AP is up I do see in the logs:
Jul 19 22:06:34 yuna kernel: brcmfmac: brcmf_fil_cmd_data Firmware
error: BCME_UNSUPPORTED (-23)
Jul 19 22:06:34 yuna kernel: brcmfmac: brcmf_configure_arp_nd_offload
failed to configure (0) ND offload err = -52
But maybe more importantly when tearing down I see:
...
Jul 19 22:07:23 yuna kernel: brcmfmac mmc2:0001:1 wlan0: left
allmulticast mode
Jul 19 22:07:23 yuna kernel: brcmfmac mmc2:0001:1 wlan0: left
promiscuous mode
...
Jul 19 22:07:23 yuna kernel: brcmfmac: brcmf_configure_arp_nd_offload
successfully configured (1) ARP offload to 0x9
Jul 19 22:07:23 yuna kernel: brcmfmac: brcmf_fil_iovar_data_set ifidx=0,
name=ndoe, len=4
...
Jul 19 22:07:23 yuna kernel: brcmfmac: brcmf_fil_cmd_data Firmware
error: BCME_UNSUPPORTED (-23)
Jul 19 22:07:23 yuna kernel: brcmfmac: brcmf_configure_arp_nd_offload
failed to configure (1) ND offload err = -52
...
This has regressed from some older kernels (it used to work fine) , but
I don't know exactly when, since I hadn't been testing AP for a while.
Any ideas are welcome to debug this. Or any patches to try, I can build
on current kernel (6.16-rc6) easily and capture logs.
Currently I am using:
echo 0x1006 > /sys/module/brcmfmac/parameters/debug
journalctl -k | grep -e brcm -e "000000" -e ieee > debug.log
Thanks
Ferry
prev parent reply other threads:[~2025-07-19 20:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 4:20 [PATCH] brcmfmac: Add an error log for brcmf_sdiod_ramrw() Wentao Liang
2025-04-20 18:15 ` Cannot maintain an ap with brcmfmac KeithG
2025-04-21 6:47 ` Arend Van Spriel
2025-07-19 20:57 ` Ferry Toth [this message]
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=dc05e447-06a1-4865-8252-c4a0710d6da9@gmail.com \
--to=fntoth@gmail.com \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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).