Re: [BUG] iwlwifi: Comet Lake PCH CNVi AX201 (8086:06f0) fails with error -110 on warm reboot

Hi Bohdan,

I ran the test in a clean live environment running a modern upstream
kernel (pure open-source drivers, no NVIDIA or out-of-tree DKMS
modules).

The behavior reproduces identically on the clean live session:
1. Cold boot: AX201 initializes and detects networks.
2. Module reload (modprobe -r iwlwifi && modprobe iwlwifi): The driver
fails during the bus reset sequence and drops the device.

Kernel log from the clean live session:
[   72.114520] iwlwifi 0000:00:14.3: Host monitor block 0x0 vector 0x6
[   72.114522] iwlwifi 0000:00:14.3:      value [iter 0]: 0x00000003
...
[   72.114548] iwlwifi 0000:00:14.3: Host monitor block 0x22 vector 0x0
[   72.114566] iwlwifi 0000:00:14.3:      value [iter 0]: 0x00000003
[   72.119890] iwlwifi 0000:00:14.3: probe with driver iwlwifi failed
with error -110

This confirms the issue occurs directly in the upstream driver's
CSR_RESET and Host Monitor polling loop during PCIe/CNVi
re-initialization on this Comet Lake PCH platform (8086:06f0,
subsystem 8086:0074), independent of proprietary display drivers or
local distribution configurations.

Please let me know if any specific kernel debug flags or register
tracepoints would help you isolate the bus timing issue.

Best,
Mark


On Thu, 27 Aug 2026 at 20:47, Bohdan <[email protected]> wrote:
>
> > Hi Bohdan and Boulder,
>
> Both are me, for some reason Thunderbird on Android decided to use "Boulder" which is Google account name. Hope this won't happen this time. Please bear with me while I debug identity settings.
>
> >I tried testing the mainline 7.1 build directly, but on this Precision 7550
> >the generic mainline image hits an early boot panic. It looks to be related
> >to the out-of-tree proprietary GPU module and its initramfs hooks, so I
> >wasn't able to get a clean 7.1 boot on this installation.
>
> We still can debug this, but you'll have to blacklist the drivers that make your system not boot (and lose the graphical interface in the meantime, or rely purely on integrated graphics during debugging if they are present) and try iwlwifi through the command line. In the worst-case scenario, you will need a USB with Linux distro ISO on it, and a guide on how to use chroot. Keep track of the changes you will have done, that way it will be easier to restore the system.
>
> If you use NetworkManager for wireless (you likely do, most Linux distros do), you can use nmtui to connect to Wi-Fi from there, which may be useful for further testing.
>
> Hope it's not NVIDIA (it will surely be NVIDIA),
> Bohdan