[brcmfmac] Pi 5 host-requested 2.4→5 GHz roam emits firmware status 19, then drops the old connection

オープン
#7,758 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
12/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
c, linux

調査の方向性

Start with the brcmfmac roam handler and the firmware-event decoding under drivers/net/wireless/broadcom/brcm80211/brcmfmac/, since the report states the handler notifies cfg80211 only on success. Reproduce the failing wpa_cli roam on the Pi 5 with join_event_debug=Y and compare against the stock-module control the reporter plans. Done means an answer on what ROAM status 19/reason 0 means for FWID 01-b677b91b, whether the join iovar is valid while associated, and a decision on reporting a failed roam so the old association survives.

索引モデルが issue の本文から書いたものです。

説明

Describe the bug

A Raspberry Pi 5 can connect from a disconnected state to the 5 GHz radio of a Zyxel EX5601-T1, but a host-requested roam from the same AP’s 2.4 GHz radio to its 5 GHz radio stalls. The behaviour was observed on channels 36 and 100.

On channel 36, an independent capture showed five probes from the Pi and replies from the AP, but no authentication, association, or reassociation frames between them. The fresh-join control on the same channel showed successful authentication, association, and a four-way handshake.

During the roam, the firmware emitted a non-success ROAM event approximately 108 ms after accepting the join command. The old association was still reported shortly before wpa_supplicant timed out and disconnected locally at about 10 seconds. Whether the old link still carried IP traffic was not measured.

Expected behaviour is either a successful roam or, if the target cannot be joined and the old link is still usable, a failed roam that leaves the old connection intact.

Steps to reproduce the behaviour
  1. Configure a dual-band Zyxel EX5601-T1 with the same SSID and security on both radios. The main test used channel 1 and channel 36, with WPA2-PSK-SHA256, CCMP, and required PMF.
  2. From a disconnected state, connect the Pi directly to the 5 GHz BSSID. Verify that wpa_supplicant reaches COMPLETED.
  3. Disconnect and connect to the 2.4 GHz BSSID. Verify the current association and confirm the 5 GHz target appears in the supplicant scan results. If the active network was pinned to 2.4 GHz, clear the runtime pin without disconnecting and verify the current association again.
  4. Run sudo wpa_cli -i wlan0 roam <TARGET_5_GHZ_BSSID>. It returns OK, but the target never reaches COMPLETED. Monitor the kernel log, supplicant log, and iw dev wlan0 link for 15 seconds.
Device (s)

Raspberry Pi 5

System
  • Raspberry Pi 5, ARM64, onboard BCM4345/6-class SDIO Wi-Fi
  • Kernel 6.12.115+rpt-rpi-2712, package 1:6.12.115-1+rpt1
  • brcmfmac with a local diagnostic module override, roamoff=1 and join_event_debug=Y
  • Wi-Fi firmware 7.45.265 (28bca26 CY), FWID 01-b677b91b
  • Access point Zyxel EX5601-T1
Logs

Channel 36, relative to the driver submitting the roam request. These are normalized excerpts, not verbatim logs.

+0.000 s   brcmfmac join iovar returned 0
+0.108 s   Firmware ROAM event, status=19, reason=0, event address all zeros
+9.078 s   iw link still reported the original 2.4 GHz association
+9.999 s   wpa_supplicant reported an authentication timeout for the target
+10.003 s  wpa_supplicant reported a locally generated disconnect
+12.889 s  Pi completed a connection to a different AP

On channel 100, the same firmware status appeared approximately 16 ms after join submission. An overnight trace contained 15 matching event-and-timeout pairs during automatic roam attempts to the same target.

Additional context

Could you confirm what firmware ROAM status 19, reason 0 means on FWID 01-b677b91b, and whether the join iovar is the intended command when already associated?

The brcmfmac roam handler appears to notify cfg80211 only on success. Is there an intended way to complete a failed host-requested roam while preserving a usable old association?

A stock-module comparison is planned. Only normalized excerpts are included to avoid disclosing identifiers from the local network and nearby networks.

主要言語
C
スター
13.3k
フォーク
5.5k
平均マージ
4日 10時間
マージ済み PR(30日)
31

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

raspberrypi/linux のほかの issue

raspberrypi/linux の issue をすべて見る

似ている issue

C の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。