Skip site navigation (1)Skip section navigation (2) 
Date:      Sat, 16 Nov 2024 15:54:11 +0000
From:      bugzilla-noreply@freebsd.org
To:        wireless@FreeBSD.org
Subject:   [Bug 282789] iwlwifi hangs on boot with request_module_nowait("iwlmvm") -- broken after 2ac644317e671b001d3fb8fd924a1ae808a0bf32
Message-ID:  <bug-282789-21060-MobaFWj7bG@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-282789-21060@https.bugs.freebsd.org/bugzilla/>
References:  <bug-282789-21060@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D282789

Bjoern A. Zeeb <bz@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|wireless@FreeBSD.org        |bz@FreeBSD.org
             Status|Open                        |In Progress
            Summary|iwlwifi broken after        |iwlwifi hangs on boot with
                   |2ac644317e671b001d3fb8fd924 |request_module_nowait("iwlm
                   |a1ae808a0bf32               |vm") -- broken after
                   |                            |2ac644317e671b001d3fb8fd924
                   |                            |a1ae808a0bf32

--- Comment #7 from Bjoern A. Zeeb <bz@FreeBSD.org> ---
Ruslan sent me debug information and I do now understand where the problem
comes from but not yet why it only happens for some chipsets only.

Or possibly not chipsets but something else;  the entire order is triggered
from SYSINITs via module_init;  in the cases of hang iwl_mvm_init() has not=
 run
(or not run to completion).

For cards here it looks like (with XXX-BZ printfs added to show the problem)

------
Autoloading module: if_iwlwifi=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
Intel(R) Wireless WiFi based driver for FreeBSD=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
XXX-BZ iwl_opmode_register:1933: name 'iwlmvm' ops 0xffffffff82ba6d38=20=20=
=20=20=20=20=20=20=20=20=20
XXX-BZ iwl_opmode_register:1940: name 'iwlmvm' ops 0xffffffff82ba6d38 op
0xffffffff82baf0e0

^^^^ this is missing for the people with "hangs"

pci0: driver added=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
found-> vendor=3D0x8086, dev=3D0x2725, revid=3D0x1a=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20
        domain=3D0, bus=3D0, slot=3D5, func=3D0=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20
        class=3D02-80-00, hdrtype=3D0x00, mfdev=3D0=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20
        cmdreg=3D0x0407, statreg=3D0x0010, cachelnsz=3D0 (dwords)=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
        lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns)=
=20=20=20=20=20=20=20=20=20=20=20=20
        powerspec 3  supports D0 D3  current D0=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
        MSI supports 1 message, 64 bit=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20
        MSI-X supports 16 messages in map 0x10=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
pci0:0:5:0: reprobing on driver added=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20
iwlwifi0: <iwlwifi> mem 0x800010000-0x800013fff at device 5.0 on pci0=20=20=
=20=20=20=20=20=20=20=20=20
iwlwifi0: attempting to allocate 6 MSI-X vectors (16 supported)=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20
msi: routing MSI-X IRQ 60 to local APIC 0 vector 57=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
msi: routing MSI-X IRQ 61 to local APIC 1 vector 51=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
msi: routing MSI-X IRQ 62 to local APIC 2 vector 52=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
msi: routing MSI-X IRQ 63 to local APIC 3 vector 51=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
msi: routing MSI-X IRQ 64 to local APIC 0 vector 58=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
msi: routing MSI-X IRQ 65 to local APIC 1 vector 52=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
iwlwifi0: using IRQs 60-65 for MSI-X=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20
iwlwifi0: Detected crf-id 0x400410, cnv-id 0x400410 wfpm id 0x80000000=20=
=20=20=20=20=20=20=20=20=20
iwlwifi0: PCI dev 2725/0024, rev=3D0x420, rfid=3D0x10d000=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
iwlwifi0: Detected Intel(R) Wi-Fi 6 AX210 160MHz=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
...
------

And so for the people where it does not work:

in iwl_req_fw_callback op->ops is not defined and it tries to load the ilwm=
vm
module ( which we don't have given we never split the driver given we do not
have dwm support ).

I'll go and investigate why we never make it to the second SYSINIT.

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

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-282789-21060-MobaFWj7bG>