public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Kaushal Kansara <kskansara79@gmail.com>
To: johannes@sipsolutions.net
Cc: linux-wireless@vger.kernel.org,
	miriam.rachel.korenblit@intel.com,  johannes.berg@intel.co,
	kaushal.kansara@sophos.com
Subject: [REGRESSION] mac80211 WARN during CSA finalize on mt7915e after 20240129194108.bad8ec1e76c8
Date: Mon, 16 Mar 2026 13:41:13 +0530	[thread overview]
Message-ID: <CAHFM2E+d6KiOfAgejK+hEUMvyAwx+uCwZLM3dVSBgjXiDoxoQQ@mail.gmail.com> (raw)

Hi all,

I’m reporting a regression seen on mt7915e during AP channel switch
handling and it is related to:

https://lore.kernel.org/all/20240129194108.bad8ec1e76c8.I12287452f42c54baf75821e75491cf6d021af20a@changeid/#t


Environment:


Kernel: 6.6.116

Driver/chipset: mt7915e

Platform: Sophos XGS

Trigger: concurrent AP CSA activity (e.g. WLAN9/WLAN10)

Observed warning:


WARNING at chan.c:92

Function in trace: ieee80211_vif_use_reserved_switch

Worker context: ieee80211_csa_finalize_work

Relevant log excerpt:


WLAN9: IEEE 802.11 driver starting channel switch: ... width=3 (80
MHz), cf1=5210, cf2=0

WLAN10: IEEE 802.11 driver starting channel switch: ... width=3 (80
MHz), cf1=5210, cf2=0

WARNING: CPU: 2 PID: 8713 at linux-kernel/net/mac80211/chan.c#L92
ieee80211_vif_use_reserved_switch+0x546/0x8d0 [mac80211]

Call trace:

ieee80211_link_use_reserved_context

__ieee80211_csa_finalize

ieee80211_csa_finalize_work

process_one_work

worker_thread


I can consistently reproduce this under CSA churn; please let me know
if you want full dmesg, .config, or additional instrumentation around
reserved channel-context transitions.


If I revert this patch, the warning goes away.

#regzbot introduced: 20240129194108.bad8ec1e76c8

#regzbot title: mac80211 WARN in ieee80211_vif_use_reserved_switch on
mt7915e during CSA finalize

#regzbot link: https://lore.kernel.org/all/20240129194108.bad8ec1e76c8.I12287452f42c54baf75821e75491cf6d021af20a@changeid/#t


Thanks,

Kaushal Kansara

                 reply	other threads:[~2026-03-16  8:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAHFM2E+d6KiOfAgejK+hEUMvyAwx+uCwZLM3dVSBgjXiDoxoQQ@mail.gmail.com \
    --to=kskansara79@gmail.com \
    --cc=johannes.berg@intel.co \
    --cc=johannes@sipsolutions.net \
    --cc=kaushal.kansara@sophos.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=miriam.rachel.korenblit@intel.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