Skip to content

j516s (MacBook Pro 16" M3 Pro): joining an OWE network traps BCM4388 firmware, Wi-Fi dead until module reload #215

Open

Description

@aronvandepol

Mac and installed build

  • MacBook Pro 16" M3 Pro, apple,j516s / apple,t6030, Arch Linux ARM + Omarchy
  • linux-aurora 7.1.12.aurora2-20261017.20, running 7.1.12-2-20261017.20-sep-gpufix-ARCH. That is the .20 source with one local GPU deferred-close patch (now merged as M3 Pro GPU crash fix: preserve new mappings during deferred GEM close #214), and the brcmfmac is unchanged from .20.
  • m1n1-aurora 1.6.1.aurora17-5, NetworkManager 1.58.1, wpa_supplicant 2.12
  • Wi-Fi: BCM4388/4, firmware 23.30.58.0.41.51.138 (FWID 01-baea9d27)

Both firmware versions and provisioning

  • asahi,os-fw-version: 14.7
  • asahi,system-fw-version: 26.6.2

Reproduction, expected result, and actual result

  1. Be in range of an OWE-only ("Enhanced Open") network. Here that was Schiphol_Free_Wi-Fi, where NM uses key-mgmt=owe and every BSS of that SSID is OWE.
  2. nmcli con up <owe-network>

Expected: it connects, or it fails and Wi-Fi keeps working.

Actual: the firmware associates (LINK up, status 0), then traps about 25 ms later. The trap never reaches the host as FWHALT, so brcmfmac does not reset. Every ioctl then times out (-5) until the control ring fills, and every command fails with -12. No network can be scanned or joined until reboot or modprobe -r brcmfmac_wcc brcmfmac && modprobe brcmfmac.

Frequency: 6 of 7 OWE attempts on 2026-10-25 trapped, on both 5 GHz and 6 GHz BSSes. The 7th failed at once without a trap. WPA2/WPA3-PSK networks work normally.

Relevant error lines

With the firmware console dumped:

brcmf_cfg80211_connect channel=100, center_req=5500
brcmf_cfg80211_connect SSID "Schiphol_Free_Wi-Fi", len (19)
brcmf_fweh_event_worker event LINK (16:16) ...              (flags 1 status 0)
CONSOLE: 000225.602 THREADX TRAP INFO:
CONSOLE: TRAP 4(8a2db980): pc 2f3a30, lr 2a2c0b, sp 8a2db9d8, cpsr 200001d3, spsr 40000033
CONSOLE: 000225.603   dfsr 7, dfar 30

Without the fix below, the stock driver then shows:

wpa_supplicant: wlan0: Authentication with <bssid> timed out.
brcmf_msgbuf_query_dcmd_len: Timeout on response for query command
brcmf_cfg80211_disconnect: error (-5)
...
brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
brcmf_cfg80211_scan: scan error (-12)

In two hung boots there were 62 ioctl timeouts each and 0 Firmware has halted lines.

Related issues, pull requests, or code examples

Host-side changes I tried. The trap stayed at the same pc 2f3a30 / dfar 30 in every case:

change to brcmfmac result
stock (wpa_auth OWE, use_fwsup ROAM) auth timeout, trap
also forward the OWE DH element (ext id 32) in the assoc-request IEs (brcmf_parse_vndr_ies only forwards vendor IEs) associates, trap
also use_fwsup = NONE for OWE (sup_wpa 0) associates, trap
wpa_auth WPA2_AUTH_UNSPECIFIED for OWE firmware rejects the join at once (SET_SSID fails), no trap

So the trap looks like it's inside the firmware's own OWE handling after association. I could not find a host setting that avoids it.

Recovery fix (tested): a small msgbuf change counts consecutive ioctl timeouts and calls brcmf_fw_crashed() at the third. That keeps the coredump and console read and schedules the existing PCIe reset. With it, Wi-Fi rejoined the previous network about 12 s after the trap, in 3 of 4 OWE attempts. Once, the reload itself failed (brcmf_c_preinit_dcmds: Retrieving cur_etheraddr failed, -5 → Dongle setup failed) and wlan0 disappeared. The branch is ready if a PR is wanted, but it needs a retry for that case first.

What was not tested

  • OWE transition-mode networks (only OWE-only)
  • Other Apple Broadcom chips (BCM4377/4378/4387)
  • Whether macOS on this Mac joins the same network (not checked)
  • Newer firmware from a later macOS

Activity

  1. jonkpub commented on Oct 26, 2026

    @jonkpub

    Additional affected hardware: BCM4387 / j314s (MacBook Pro 14-inch M1 Pro). This adds the BCM4387 case currently listed as untested in this issue. The failure matches the authentication timeout, subsequent unresponsive firmware, and module-reload recovery described above; a firmware console trap has NOT been captured on this machine.

    Mac and installed build

    • MacBookPro18,3 / apple,j314s, Arch Linux ARM + Omarchy.
    • Installed linux-aurora 7.1.12.aurora2-20261017.20; running 7.1.12-2-20261017.20-sep-ARCH.
    • Kernel source listed by the release: c46d7dc.
    • m1n1-aurora package 1.6.1.aurora17-5; omarchy-dev 4.0.4.r7099.gb8ed395-1.
    • NetworkManager 1.58.1-2, iwd 3.12-2, wpa_supplicant 2:2.12-1.
    • Broadcom BCM4387 [14e4:4433], firmware 20.96.31.0.8.7.148, FWID 01-126f2c4c (May 27 2023).
    • brcmfmac is the native .20 kernel module. brcmfmac-awdl-dkms 0.9.0 is installed but DKMS reports only added, and the module selected by modinfo is under kernel/drivers/net/wireless/broadcom/brcm80211/brcmfmac, not updates/dkms.
    • An additional local SEP-only APFS fix package is installed (linux-aurora-sep-apfs-fix 20261025-1); there were no local Wi-Fi driver changes in these tests.

    Firmware versions

    • asahi,os-fw-version: 13.5
    • asahi,system-fw-version: unknown (the literal value reported by the device tree).
    • Wi-Fi firmware and platform calibration load successfully. Firmware provisioning was not changed during these tests.

    Reproduction and results on 2026-10-26

    PUBLIXGUEST: all 16 BSSs visible in a raw scan advertised OWE, CCMP, and MFP-required. Both 2.4 GHz and 5 GHz BSSs were visible; the attempted target was a strong 5 GHz BSS (5280 MHz, approximately -50 dBm).

    1. With NetworkManager's iwd backend and the pre-existing [DriverQuirks] OweDisable=brcmfmac setting, connecting is rejected immediately with net.connman.iwd.NotSupported. Direct iwctl connection fails identically.
    2. Back up the iwd configuration, remove that quirk, restart iwd, and activate the saved guest profile. iwd selects the BSS and enters connecting, but never completes the connection. Subsequent brcmfmac commands time out.
    3. Switch NetworkManager temporarily to wpa_supplicant, unload/reload brcmfmac_wcc and brcmfmac, and try a separate profile with 802-11-wireless-security.key-mgmt=owe and 802-11-wireless-security.pmf=3 (required). wpa_supplicant logs key_mgmt=OWE, ieee80211w=2, and owe_only=1; authentication times out. Firmware command timeouts and failed scans then recur. No Wi-Fi IP address is obtained.

    Expected: an OWE association and DHCP lease, or a clean connection failure that leaves Wi-Fi usable.

    Observed: one explicit connection test with each OWE-enabled backend failed; both were followed by firmware command timeouts. Reloading the driver recovers scanning. Switching backends alone does not resolve the connection. Original configuration was restored and the temporary profile removed after testing.

    Relevant errors (identifying addresses omitted)

    Network.Connect failed: GDBus.Error:net.connman.iwd.NotSupported: Operation not supported
    wlan0: Authentication with <redacted-bssid> timed out.
    ieee80211 phy1: brcmf_msgbuf_query_dcmd_len: Timeout on response for query command
    ieee80211 phy1: brcmf_run_escan: error (-5)
    ieee80211 phy1: brcmf_cfg80211_scan: scan error (-5)
    ieee80211 phy1: brcmf_cfg80211_get_tx_power: error (-5)
    

    Concrete driver lead to investigate (not runtime-tested)

    In the .20 source, brcmf_set_wpa_version() selects WPA3_AUTH_OWE. brcmf_set_key_mgmt() initializes profile->use_fwsup to NONE, but the condition enclosing its case WLAN_AKM_SUITE_OWE checks only WPA2_AUTH_PSK | WPA2_AUTH_UNSPECIFIED | WPA2_AUTH_1X_SHA256. If the firmware returns only WPA3_AUTH_OWE, that OWE case is skipped and the intended ROAM firmware-supplicant setting is not selected. The later connect path consequently writes sup_wpa=0 for NONE. This is source-level analysis; the runtime wpa_auth/sup_wpa values have not been instrumented here.

    • .20 key-management gate and OWE case.
    • Infineon's Enable Internal supplicant for OWE AKM adds WPA3_AUTH_OWE to that gate.
    • Infineon's Add Support for OWE offload detects the firmware owe capability, advertises NL80211_EXT_FEATURE_OWE_OFFLOAD with firmware handshake support, and clears the userspace wpaie before an offloaded OWE join. These complete offload steps are absent from the .20 source inspected here. These vendor patches are implementation references, NOT evidence of BCM4387 firmware compatibility.

    Proposed next experiment: instrument the actual firmware capability string and OWE wpa_auth/sup_wpa path, then test the missing key-management gate plus capability-gated OWE offload on a reversible brcmfmac-only build with wpa_supplicant. If the firmware lacks the capability or still traps with correct offload setup, investigate newer own-Mac firmware and report the trap to the firmware/Asahi maintainers. Keep timeout-triggered recovery as a separate fix: recovery does not establish OWE connectivity.

    Not tested

    • Firmware console/coredump or exact trap PC on BCM4387; no proof yet that the trap is identical to BCM4388.
    • The vendor fixes above, actual firmware owe capability, or runtime wpa_auth/sup_wpa instrumentation.
    • A controlled OWE AP, a connection locked to 2.4 GHz, OWE transition mode, or newer firmware.
    • Joining the same AP in macOS, DHCP/captive portal over Wi-Fi, or reconnect/suspend tests after a successful OWE join (no join succeeded).
    • No last-known-good OWE build has been established on this Mac.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions