Follow-up for @Owen Yaggy's kernel-regression theory (comment #23):
the no-precursor s2idle hang is still happening on this system, on a
newer kernel, with the original Intel AX211/CNVi hardware completely
out of the picture - so whatever this is, it doesn't look specific to
that chip.

2026-10-15 18:48:14 JST: suspend requested, teardown completely normal
(WiFi - now a Buffalo USB adapter on rtw88, not the Intel AX211 -
disconnected cleanly, no errors), systemd successfully froze
user.slice, then `kernel: PM: suspend entry (s2idle)` with nothing
else ever logged. Forced power-off required, identical to every other
instance of this pattern since the original report.

Kernel is 7.0.0-38-generic here (up from .34, where I first saw this
recur after removing the Intel WiFi entirely) - so on this machine the
hang has persisted across at least three point releases (.31, .34,
.38), independent of the specific WiFi chip involved. Adding this in
case it's useful for narrowing down where in the suspend path the
regression actually lives.

One note given this bug was just retargeted to
linux-firmware-intel-wireless: that package is the right home for the
crash-loop part of the original report (that one genuinely is
Intel-firmware-specific), but the suspend-hang part isn't - as above,
it reproduces with no Intel hardware involved at all. Might be worth
tracking that half against the kernel itself rather than assuming it's
scoped to Intel firmware.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2167666

Title:
  Intel AX211 (0000:00:14.3) iwlwifi firmware crash (ADVANCED_SYSASSERT)
  after resume causes s2idle suspend to hang; does not reproduce on
  Windows 11 on same hardware

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware-intel-wireless/+bug/2167666/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to