[Bug 282789] iwlwifi broken after 2ac644317e671b001d3fb8fd924a1ae808a0bf32

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282789

            Bug ID: 282789
           Summary: iwlwifi broken after
                    2ac644317e671b001d3fb8fd924a1ae808a0bf32
           Product: Base System
           Version: CURRENT
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: wireless
          Assignee: wireless@FreeBSD.org
          Reporter: rm@FreeBSD.org

Created attachment 255206
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=255206&action=edit
boot hang

Hello, that's the last revision when my wireless connection worked:

==========
commit 65691b2dafda23691c3989749def755a98e731ec (HEAD)
Author: Robert William Vesterman <bob@vesterman.com>
Date:   Thu Oct 17 22:54:39 2024 -0400

        libexec/rc/rc.d/netif: Typo fix
==========

If I fetch the next couple of wifi related commits, then system just stops
booting at iwlwifi initialization stage. See attached screenshot.

Minimal commit I tested, after that wifi breaks is:

==========
commit 878ede1a0d0f10f851b2bc54be1e28f512bfc016
Author: Mark Johnston <markj@FreeBSD.org>
Date:   Mon Oct 28 13:51:58 2024 +0000

    fstyp: Fix some memory safety bugs
==========


Last commit I tested, to not avail:
==========
commit 12fc79619acaa3041f9c032bc9afe7d2005b942e (HEAD -> main, origin/main,
origin/HEAD)
Author: Randall Stewart <rrs@FreeBSD.org>
Date:   Fri Nov 15 12:37:05 2024 -0500

    Change the SOCKBUF_LOCK calls to use the more refined
SOCK_XXXBUF_LOCK/UNLOCK.
==========

I also tried to install wifi-firmware-iwlwifi-kmod-20241017_1.

That's my adapter:
==========
iwlwifi0@pci0:0:20:3:   class=0x028000 rev=0x00 hdr=0x00 vendor=0x8086
device=0x02f0 subvendor=0x8086 subdevice=0x0070
    vendor     = 'Intel Corporation'
    device     = 'Comet Lake PCH-LP CNVi WiFi'
    class      = network
==========

Since I don't see any complains in mailing list about this issue, it looks like
something my particular chipset, so please help me to figure out what's wrong.

-- 
You are receiving this mail because:
You are the assignee for the bug.