From: Branislav Klocok <branislav.klocok@ofz.sk>
To: Johannes Berg <johannes@sipsolutions.net>, regressions@lists.linux.dev
Cc: linux-wireless@vger.kernel.org
Subject: Re: [REGRESSION] iwlwifi 8265 firmware ADVANCED_SYSASSERT in PHY_CONTEXT_CMD on roam (v7.0.3..v7.0.5)
Date: Wed, 13 May 2026 13:40:45 +0200 [thread overview]
Message-ID: <c867401c-bfc5-4e9f-b78e-be5348b2a776@ofz.sk> (raw)
In-Reply-To: <34084815328ea9ea00893e9aa46962d369d213e3.camel@sipsolutions.net>
[-- Attachment #1.1: Type: text/plain, Size: 2725 bytes --]
Hi Johannes,
Thanks for the quick check. I dug a bit further; the v7.0.3..v7.0.5
window is what I empirically see (clean -> crashing on every
controller-driven roam), but the cause likely sits outside iwlwifi as
you suggested.
What I can confirm from the openSUSE Tumbleweed packaging side:
- Between kernel-default-7.0.3-1.1 (installed 2026-05-08 21:45) and
7.0.5-1.1 (2026-05-10 21:25), only the kernel package changed.
kernel-firmware-intel was bumped to 20260505-1.1 in the same transaction
as 7.0.3 on 2026-05-08 and stayed unchanged across the 7.0.5 install
(8265 ucode 36.c8e8e144.0 is identical in both dmesg banners).
NetworkManager 1.54.3-3.4 and wpa_supplicant 2.11-6.3 were last touched
on 2026-05-04, also unchanged across this window. Userspace and firmware
blob can be ruled out as the trigger.
- The only iwlwifi-touching SUSE patch added between the 7.0.3 and 7.0.5
source packages is iwlwifi-declare-missing-firmware-files.patch in
7.0.4, which is metadata-only (it just adds MODULE_FIRMWARE() entries).
The rest of the diff is plain stable v7.0.3..v7.0.5.
- Caveat on my "7.0.3 worked" claim: it is based on a short boot into
7.0.3 on 2026-05-11 before booting 7.0.5; I will re-test 7.0.3 over a
longer window with forced roams to be sure.
Crash itself: ADVANCED_SYSASSERT (0x000014FD) + NMI_INTERRUPT_LMAC_FATAL
(0x70) on PHY_CONTEXT_CMD during nl80211_authenticate. ~87 % of
controller-driven roams trigger it (14/16 observed); cascading restart
loops (6x in 23 s) on bad days. NM powersave=2 (CAM) does not suppress
it. Full journal at https://bugzilla.kernel.org/show_bug.cgi?id=221512
(attachment 310106).
A couple of questions, if you have a moment:
1. Is there an iwlmvm debug knob you'd like enabled on the next
reproduction (iwlwifi.debug=, devcoredump, fw_dbg_collect) to capture
more on what PHY_CONTEXT_CMD is hitting?
2. Given iwlwifi/mac80211 is unchanged, would you point at a tighter
candidate area in v7.0.3..v7.0.5 (PCI PM, firmware loader, scheduler)
before I attempt a bisect across the full tree?
*-- *
S pozdravom / Best regards
*Branislav Klocok *
*generálny riaditeľ / general director *
* OFZ, a.s.*
Mobil: *+421 908 703 366*
Tel: *+421 43 5804 488 *
e-mail: **branislav.klocok@ofz.sk* <mailto:branislav.klocok@ofz.sk> *
web: **www.ofz.company* <http://www.ofz.company> *
ofz logo
Dňa 13. 5. 2026 o 12:41 Johannes Berg napísal(a):
> On Wed, 2026-05-13 at 12:35 +0200, Branislav Klocok wrote:
>> #regzbot introduced: v7.0.3..v7.0.5
> That cannot be right, there are no patches for wifi between those except
> a handful in drivers you're not running.
>
> johannes
[-- Attachment #1.2.1: Type: text/html, Size: 5836 bytes --]
[-- Attachment #1.2.2: FWbyySErjYKwOByv.png --]
[-- Type: image/png, Size: 4675 bytes --]
[-- Attachment #2: Kryptografický podpis S/MIME --]
[-- Type: application/pkcs7-signature, Size: 4669 bytes --]
next prev parent reply other threads:[~2026-05-13 11:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 10:35 [REGRESSION] iwlwifi 8265 firmware ADVANCED_SYSASSERT in PHY_CONTEXT_CMD on roam (v7.0.3..v7.0.5) Branislav Klocok
2026-05-13 10:41 ` Johannes Berg
2026-05-13 11:40 ` Branislav Klocok [this message]
2026-05-13 10:58 ` Branislav Klocok
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=c867401c-bfc5-4e9f-b78e-be5348b2a776@ofz.sk \
--to=branislav.klocok@ofz.sk \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=regressions@lists.linux.dev \
/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