Intel Comet Lake Wifi (8086:02f0) only working after cold start, failed with error -110

Intel Comet Lake Wifi (8086:02f0) only working after cold start, failed with error -110

[Marc Haber]

Hi,

I recently bought a used ThinkPad X13 1st Generation. That one is
equipped with an:
00:14.3 Network controller [0280]: Intel Corporation Comet Lake PCH-LP CNVi WiFi[8086:02f0]

(lspci output avaible online as https://www.zugschlus.de/stuff/lspci-v
and https://www.zugschlus.de/stuff/lspci-nn)

I can reproduce the following behavior with all Linux kernels beginning
with the one that is in Debian Stable (didn't try anything older than
that), Debian unstable, current Linux Mint, Fedora Workstation 41, up to
a self-compiled Linux 6.12.5).

While there was a Windows installed on the box when I got it, I do not
intend to dual boot the machine, and Windows has been erased by
installing the first Linux over it. Hence, I dont consider the hints
found on the Internet regarding Windows fast startup applicable in my
case. In any case, I disabled Windows fast startup before overwriting
Windows.

When the notebook is freshly cold booted (machine OFF, no led blinking,
pulsing or anything, power supply disconnected), Wifi works. When I just
reboot the machine without turning it actually off, or turn it off while
leaving the power supply connected, Wifi does not work. The Wifi chip
still shows up in lspci but not in ip addr / ip link. dmesg looks like
it does not even try uploading firmware.

In the non-working case, I see a bunch of lines like
[    3.998476] iwlwifi 0000:00:14.3: CSR_RESET = 0x10
[    3.998494] iwlwifi 0000:00:14.3: Host monitor block 0x0 vector 0x0
[    3.998524] iwlwifi 0000:00:14.3:     value [iter 0]: 0x00000000
[    3.998545] iwlwifi 0000:00:14.3:     value [iter 1]: 0x00000000
[    3.998566] iwlwifi 0000:00:14.3:     value [iter 2]: 0x00000000
[    3.998587] iwlwifi 0000:00:14.3:     value [iter 3]: 0x00000000
[    3.998608] iwlwifi 0000:00:14.3:     value [iter 4]: 0x00000000
ending with
[    4.007732] iwlwifi 0000:00:14.3: probe with driver iwlwifi failed with error -110

(full output on https://www.zugschlus.de/stuff/dmesg-notwork)

For reference, see dmesg output for a working case on
https://www.zugschlus.de/stuff/dmesg-work.

As per the instructions given on
https://wireless.docs.kernel.org/en/latest/en/users/drivers/iwlwifi/debugging.html,
I have not yet upped the debug level. I am prepared to try with a kernel
that has CONFIG_IWLWIFI_DEVICE_TRACING and/or CONFIG_IWLWIFI_DEBUG set.
If you ask me to do this, please give me instructions about how to
enable the desired debugging if module parameters, kernel command line
parameters etc are necessary.

I would apprecaite any help. I can keep the machine in the current state
for a few days, I only need it after chrismas.

Please keep me on Cc, I am not subscribed to the mailing lists.

Greetings
Marc


-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany    |  lose things."    Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Re: Intel Comet Lake Wifi (8086:02f0) only working after cold start, failed with error -110

[Marc Haber]

No takers after half a week?

Greetings
Marc

On Sun, Dec 15, 2024 at 10:15:19PM +0100, Marc Haber wrote:
> I recently bought a used ThinkPad X13 1st Generation. That one is
> equipped with an:
> 00:14.3 Network controller [0280]: Intel Corporation Comet Lake PCH-LP CNVi WiFi[8086:02f0]
> 
> (lspci output avaible online as https://www.zugschlus.de/stuff/lspci-v
> and https://www.zugschlus.de/stuff/lspci-nn)
> 
> I can reproduce the following behavior with all Linux kernels beginning
> with the one that is in Debian Stable (didn't try anything older than
> that), Debian unstable, current Linux Mint, Fedora Workstation 41, up to
> a self-compiled Linux 6.12.5).
> 
> While there was a Windows installed on the box when I got it, I do not
> intend to dual boot the machine, and Windows has been erased by
> installing the first Linux over it. Hence, I dont consider the hints
> found on the Internet regarding Windows fast startup applicable in my
> case. In any case, I disabled Windows fast startup before overwriting
> Windows.
> 
> When the notebook is freshly cold booted (machine OFF, no led blinking,
> pulsing or anything, power supply disconnected), Wifi works. When I just
> reboot the machine without turning it actually off, or turn it off while
> leaving the power supply connected, Wifi does not work. The Wifi chip
> still shows up in lspci but not in ip addr / ip link. dmesg looks like
> it does not even try uploading firmware.
> 
> In the non-working case, I see a bunch of lines like
> [    3.998476] iwlwifi 0000:00:14.3: CSR_RESET = 0x10
> [    3.998494] iwlwifi 0000:00:14.3: Host monitor block 0x0 vector 0x0
> [    3.998524] iwlwifi 0000:00:14.3:     value [iter 0]: 0x00000000
> [    3.998545] iwlwifi 0000:00:14.3:     value [iter 1]: 0x00000000
> [    3.998566] iwlwifi 0000:00:14.3:     value [iter 2]: 0x00000000
> [    3.998587] iwlwifi 0000:00:14.3:     value [iter 3]: 0x00000000
> [    3.998608] iwlwifi 0000:00:14.3:     value [iter 4]: 0x00000000
> ending with
> [    4.007732] iwlwifi 0000:00:14.3: probe with driver iwlwifi failed with error -110
> 
> (full output on https://www.zugschlus.de/stuff/dmesg-notwork)
> 
> For reference, see dmesg output for a working case on
> https://www.zugschlus.de/stuff/dmesg-work.
> 
> As per the instructions given on
> https://wireless.docs.kernel.org/en/latest/en/users/drivers/iwlwifi/debugging.html,
> I have not yet upped the debug level. I am prepared to try with a kernel
> that has CONFIG_IWLWIFI_DEVICE_TRACING and/or CONFIG_IWLWIFI_DEBUG set.
> If you ask me to do this, please give me instructions about how to
> enable the desired debugging if module parameters, kernel command line
> parameters etc are necessary.
> 
> I would apprecaite any help. I can keep the machine in the current state
> for a few days, I only need it after chrismas.
> 
> Please keep me on Cc, I am not subscribed to the mailing lists.
> 
> Greetings
> Marc
> 
> 
> -- 
> -----------------------------------------------------------------------------
> Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
> Leimen, Germany    |  lose things."    Winona Ryder | Fon: *49 6224 1600402
> Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany    |  lose things."    Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Re: Intel Comet Lake Wifi (8086:02f0) only working after cold start, failed with error -110

[Sedat Dilek]

On Thu, Dec 19, 2024 at 4:11 PM Marc Haber <mh+linux-kernel@zugschlus.de> wrote:
>
> No takers after half a week?
>
> Greetings
> Marc
>

[ CC Miriam + JoHill ]

Hi Marc,

I enhanced the CC list.

Hmm... Is the T: tag still valid?

T: git git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi.git

Checked for newer firmware?

Thanks.

Best regards,
-Sedat-

[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/MAINTAINERS#n11911
[2] https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/

> On Sun, Dec 15, 2024 at 10:15:19PM +0100, Marc Haber wrote:
> > I recently bought a used ThinkPad X13 1st Generation. That one is
> > equipped with an:
> > 00:14.3 Network controller [0280]: Intel Corporation Comet Lake PCH-LP CNVi WiFi[8086:02f0]
> >
> > (lspci output avaible online as https://www.zugschlus.de/stuff/lspci-v
> > and https://www.zugschlus.de/stuff/lspci-nn)
> >
> > I can reproduce the following behavior with all Linux kernels beginning
> > with the one that is in Debian Stable (didn't try anything older than
> > that), Debian unstable, current Linux Mint, Fedora Workstation 41, up to
> > a self-compiled Linux 6.12.5).
> >
> > While there was a Windows installed on the box when I got it, I do not
> > intend to dual boot the machine, and Windows has been erased by
> > installing the first Linux over it. Hence, I dont consider the hints
> > found on the Internet regarding Windows fast startup applicable in my
> > case. In any case, I disabled Windows fast startup before overwriting
> > Windows.
> >
> > When the notebook is freshly cold booted (machine OFF, no led blinking,
> > pulsing or anything, power supply disconnected), Wifi works. When I just
> > reboot the machine without turning it actually off, or turn it off while
> > leaving the power supply connected, Wifi does not work. The Wifi chip
> > still shows up in lspci but not in ip addr / ip link. dmesg looks like
> > it does not even try uploading firmware.
> >
> > In the non-working case, I see a bunch of lines like
> > [    3.998476] iwlwifi 0000:00:14.3: CSR_RESET = 0x10
> > [    3.998494] iwlwifi 0000:00:14.3: Host monitor block 0x0 vector 0x0
> > [    3.998524] iwlwifi 0000:00:14.3:     value [iter 0]: 0x00000000
> > [    3.998545] iwlwifi 0000:00:14.3:     value [iter 1]: 0x00000000
> > [    3.998566] iwlwifi 0000:00:14.3:     value [iter 2]: 0x00000000
> > [    3.998587] iwlwifi 0000:00:14.3:     value [iter 3]: 0x00000000
> > [    3.998608] iwlwifi 0000:00:14.3:     value [iter 4]: 0x00000000
> > ending with
> > [    4.007732] iwlwifi 0000:00:14.3: probe with driver iwlwifi failed with error -110
> >
> > (full output on https://www.zugschlus.de/stuff/dmesg-notwork)
> >
> > For reference, see dmesg output for a working case on
> > https://www.zugschlus.de/stuff/dmesg-work.
> >
> > As per the instructions given on
> > https://wireless.docs.kernel.org/en/latest/en/users/drivers/iwlwifi/debugging.html,
> > I have not yet upped the debug level. I am prepared to try with a kernel
> > that has CONFIG_IWLWIFI_DEVICE_TRACING and/or CONFIG_IWLWIFI_DEBUG set.
> > If you ask me to do this, please give me instructions about how to
> > enable the desired debugging if module parameters, kernel command line
> > parameters etc are necessary.
> >
> > I would apprecaite any help. I can keep the machine in the current state
> > for a few days, I only need it after chrismas.
> >
> > Please keep me on Cc, I am not subscribed to the mailing lists.
> >
> > Greetings
> > Marc
> >
> >
> > --
> > -----------------------------------------------------------------------------
> > Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
> > Leimen, Germany    |  lose things."    Winona Ryder | Fon: *49 6224 1600402
> > Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421
>
> --
> -----------------------------------------------------------------------------
> Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
> Leimen, Germany    |  lose things."    Winona Ryder | Fon: *49 6224 1600402
> Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421
>

Re: Intel Comet Lake Wifi (8086:02f0) only working after cold start, failed with error -110

[Marc Haber]

Hi,

On Thu, Dec 19, 2024 at 04:34:03PM +0100, Sedat Dilek wrote:
> I enhanced the CC list.

That would have been my next escalation. Thanks for doing it quicker.

> Checked for newer firmware?

Debian Unstable has firmware-iwlwifi dated 20240909.

And, in the "bad" case, the syslog doesn't look like something is even
trying to download firmware.

Greetings
Marc

-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany    |  lose things."    Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Re: Intel Comet Lake Wifi (8086:02f0) only working after cold start, failed with error -110

[Marc Haber]

On Fri, Dec 20, 2024 at 08:09:48AM +0100, Marc Haber wrote:
> On Thu, Dec 19, 2024 at 04:34:03PM +0100, Sedat Dilek wrote:
> > I enhanced the CC list.
> 
> That would have been my next escalation. Thanks for doing it quicker.
> 
> > Checked for newer firmware?
> 
> Debian Unstable has firmware-iwlwifi dated 20240909.
> 
> And, in the "bad" case, the syslog doesn't look like something is even
> trying to download firmware.

I updated my Debian unstable from last week's version, it now has kernel
6.12.5 and firmware-iwlwifi-20241210_all.deb. Behavior unchanged.

I then downloaded linux-firmware-iwlwifi-fw-2024-11-28.tar.gz and copied
its contents over /lib/firmware. Behaviod unchanged.

In the bad case, grepping dmesg for firmware yields firmware being
loadded for psmouse, Bluetooth, elan_i2c, and sof-audio-pci-intel-cnl,
but not for iwlwifi.

In the good case, it additionally logs failure to load
iwl-debug-yoyo.bin (-2) and then proceeds to successfully load firmware
version 77.0b4c06ad.0 QuZ-a0-hr-b0-77.ucode op_mode iwlmvm.

Greetings
Marc

-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany    |  lose things."    Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421