Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
The system was running Debian 13 with the backports kernel 7.1.8-1~bpo13+1 on an amd64 ThinkPad system.
The Wi-Fi interface (wlp3s0) is provided by the Intel iwlwifi driver (0000:03:00.0). The interface initially connects to the access point successfully.
The problem occurs when the Wi-Fi interface is restarted or reconfigured. For example, restarting the interface/network connection causes a kernel panic. The
issue appears to be related to the iwlwifi driver while it is stopping, restarting, or reconfiguring the Wi-Fi device.
The system also has the out-of-tree thinkpad_ec and tp_smapi modules loaded, so the kernel is tainted with O and E.
* What exactly did you do (or not do) that was effective (or
ineffective)?
The Wi-Fi device is:
PCI device: 03:00.0
Driver: iwlwifi
Interface: wlp3s0
The interface initially connects normally:
wlp3s0: authenticate with d6:31:27:9e:f0:b7
wlp3s0: authenticated
wlp3s0: associated
After subsequently restarting or reconfiguring the Wi-Fi interface, the kernel panics.
* What was the outcome of this action?
The kernel panics during the Wi-Fi restart/reconfiguration operation, resulting in a system hang/crash and requiring a reboot.
The normal Wi-Fi operation before the restart works correctly.
The supplied kernel log shows repeated initialization messages from iwlwifi, including:
iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
However, the supplied boot/runtime log does not contain the kernel panic backtrace itself.
* What outcome did you expect instead?
Restarting or reconfiguring wlp3s0 should cause the Wi-Fi driver to stop and reinitialize the device without crashing the kernel. The interface should become
available again and reconnect to the configured wireless network.
Hi Rasya, Thanks for the report! One thing to clarify first: the fatal crash in your log is not actually in the Wi-Fi driver. The iwlwifi/iwldvm "FW Error" messages at 817.795 are non-fatal noise. The panic ~120ms later is a NULL function-pointer call in i915 (the graphics driver): RIP: 0010:0x0 signal_irq_work+0x28a/0x570 [i915] Kernel panic - not syncing: Fatal exception in interrupt So this looks like an i915 crash that may or may not be related to the Wi-Fi activity. Also note the kernel is tainted by out-of-tree modules (thinkpad_ec, tp_smapi, hdaps, acpi_call), which can corrupt unrelated subsystems, so we can't yet treat this as a Debian kernel bug. To move forward, could you please: 1. Reproduce with those out-of-tree DKMS modules unloaded/blacklisted, and confirm with "lsmod" that none are loaded. Does it still panic? 2. Tell us the exact command(s) you run to "restart / reconfigure" the Wi-Fi (e.g. "nmcli radio wifi off/on", "ip link set wlp3s0 down/up", restarting NetworkManager, suspend/resume), and how reliably it reproduces. 3. Retest on the current backports kernel 7.1.13-1~bpo13+1 (you are on 7.1.8). Thanks, Yunseong