Date: Tue, 29 Mar 2022 17:14:28 +0300 From: Oleksandr Kryvulia <shuriku@shurik.kiev.ua> To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Cc: wireless@freebsd.org Subject: Re: iwlwifi failed to attach Message-ID: <89fa7191-30aa-e550-0e5d-d061c985c5ab@shurik.kiev.ua> In-Reply-To: <alpine.BSF.2.00.2203291324050.68830@ai.fobar.qr> References: <85f3cdd5-9bcc-426b-55e8-f3964de87c52@shurik.kiev.ua> <alpine.BSF.2.00.2203291300170.68830@ai.fobar.qr> <87e39641-f6c2-3306-e89d-fe6ba5a8ff39@shurik.kiev.ua> <alpine.BSF.2.00.2203291324050.68830@ai.fobar.qr>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --]
29.03.22 16:31, Bjoern A. Zeeb пишет:
> On Tue, 29 Mar 2022, Oleksandr Kryvulia wrote:
>
>> 29.03.22 16:02, Bjoern A. Zeeb пишет:
>>> On Tue, 29 Mar 2022, Oleksandr Kryvulia wrote:
>>>
>>>> When attaching iwlwifi module according to [1] on CURRENT
>>>> (main-n253905-31e076d70b5-dirty
>>>> ) I get an error:
>>>>
>>>> Mar 29 15:10:31 thinkpad kernel: iwlwifi0: <iwlwifi> mem
>>>> 0xdd638000-0xdd63bfff at device 20.3 on pci0
>>>> Mar 29 15:10:31 thinkpad kernel: iwlwifi0: HW_REV=0xFFFFFFFF, PCI
>>>> issues?
>>>> Mar 29 15:10:31 thinkpad kernel: device_attach: iwlwifi0 attach
>>>> returned 5
>>>
>>> Can you show a full pciconf -lBbcevV of the device at this point?
>> iwm0@pci0:0:20:3: class=0x028000 rev=0x30 hdr=0x00
>> vendor=0x8086 device=0x9df0 subvendor=0x8086 subdevice=0x0034
>
> That has iwm0 attached again. Something else is going wrong then.
>
>
>> vendor = 'Intel Corporation'
>> device = 'Cannon Point-LP CNVi [Wireless-AC]'
>> class = network
>> bar [10] = type Memory, range 64, base 0xdd638000, size 16384,
>> enabled
>> cap 01[c8] = powerspec 3 supports D0 D3 current D0
>> cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message
>> cap 10[40] = PCI-Express 2 root endpoint max data 128(128) FLR RO NS
>> max read 128
>> cap 11[80] = MSI-X supports 16 messages
>> Table in map 0x10[0x2000], PBA in map 0x10[0x3000]
>> ecap 0000[100] = unknown 0
>> ecap 0018[14c] = LTR 1
>> ecap 000b[164] = Vendor [1] ID 0010 Rev 0 Length 20
>>
>>
>>>
>>>
>>> Alternatively to try:
>>>
>>> What happens if you add if_iwm to devmatch_blocklist="" in rc.conf and
>>> boot; does iwlwifi attach fine then automatically during multi-user
>>> boot
>>> time?
>>>
>> Same error. I tried to remove if_iwm.ko from /boot/kernel and boot ))
>
> iwm(4) is likely compiled into the kernel... forgive me. You can
> proabbly
> try
> hint.iwm.disabled="1"
> or
> hint.iwm.0.disabled="1"
>
> in loader.conf and see if that helps or compile a kernel without iwm
> and iwmfw to test.
Ok, boot with iwm disabled:
root@thinkpad:/ # kldstat -v | grep -e 'iw[ml]'
26 1 0xffffffff83b3f000 88070 if_iwlwifi.ko
(/boot/kernel/if_iwlwifi.ko)
526 pci/lkpi_iwl_hw_card_ids
pciconf -lBbcevV:
none3@pci0:0:20:3: class=0x028000 rev=0x30 hdr=0x00 vendor=0x8086
device=0x9df0 subvendor=0x8086 subdevice=0x0034
vendor = 'Intel Corporation'
device = 'Cannon Point-LP CNVi [Wireless-AC]'
class = network
bar [10] = type Memory, range 64, base 0xdd638000, size 16384,
disabled
cap 01[c8] = powerspec 3 supports D0 D3 current D3
cap 05[d0] = MSI supports 1 message, 64 bit
cap 10[40] = PCI-Express 2 root endpoint max data 128(128) FLR RO NS
max read 128
cap 11[80] = MSI-X supports 16 messages
Table in map 0x10[0x2000], PBA in map 0x10[0x3000]
ecap 0000[100] = unknown 0
ecap 0018[14c] = LTR 1
ecap 000b[164] = Vendor [1] ID 0010 Rev 0 Length 20
Attach iwlwifi:
root@thinkpad:/ # devctl set driver pci0:0:20:3 iwlwifi
devctl: Failed to set pci0:0:20:3 driver to iwlwifi: Input/output error
dmesg -a:
iwlwifi0: <iwlwifi> mem 0xdd638000-0xdd63bfff at device 20.3 on pci0
iwlwifi0: HW_REV=0xFFFFFFFF, PCI issues?
device_attach: iwlwifi0 attach returned 5
[-- Attachment #2 --]
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
29.03.22 16:31, Bjoern A. Zeeb пишет:<br>
<blockquote type="cite"
cite="mid:alpine.BSF.2.00.2203291324050.68830@ai.fobar.qr">On Tue,
29 Mar 2022, Oleksandr Kryvulia wrote: <br>
<br>
<blockquote type="cite">29.03.22 16:02, Bjoern A. Zeeb пишет: <br>
<blockquote type="cite">On Tue, 29 Mar 2022, Oleksandr Kryvulia
wrote: <br>
<br>
<blockquote type="cite">When attaching iwlwifi module
according to [1] on CURRENT (main-n253905-31e076d70b5-dirty
<br>
) I get an error: <br>
<br>
Mar 29 15:10:31 thinkpad kernel: iwlwifi0: <iwlwifi>
mem 0xdd638000-0xdd63bfff at device 20.3 on pci0 <br>
Mar 29 15:10:31 thinkpad kernel: iwlwifi0:
HW_REV=0xFFFFFFFF, PCI issues? <br>
Mar 29 15:10:31 thinkpad kernel: device_attach: iwlwifi0
attach returned 5 <br>
</blockquote>
<br>
Can you show a full pciconf -lBbcevV of the device at this
point? <br>
</blockquote>
iwm0@pci0:0:20:3: class=0x028000 rev=0x30 hdr=0x00
vendor=0x8086 device=0x9df0 subvendor=0x8086 subdevice=0x0034 <br>
</blockquote>
<br>
That has iwm0 attached again. Something else is going wrong then.
<br>
<br>
<br>
<blockquote type="cite"> vendor = 'Intel Corporation' <br>
device = 'Cannon Point-LP CNVi [Wireless-AC]' <br>
class = network <br>
bar [10] = type Memory, range 64, base 0xdd638000, size
16384, enabled <br>
cap 01[c8] = powerspec 3 supports D0 D3 current D0 <br>
cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1
message <br>
cap 10[40] = PCI-Express 2 root endpoint max data 128(128)
FLR RO NS <br>
max read 128 <br>
cap 11[80] = MSI-X supports 16 messages <br>
Table in map 0x10[0x2000], PBA in map
0x10[0x3000] <br>
ecap 0000[100] = unknown 0 <br>
ecap 0018[14c] = LTR 1 <br>
ecap 000b[164] = Vendor [1] ID 0010 Rev 0 Length 20 <br>
<br>
<br>
<blockquote type="cite"> <br>
<br>
Alternatively to try: <br>
<br>
What happens if you add if_iwm to devmatch_blocklist="" in
rc.conf and <br>
boot; does iwlwifi attach fine then automatically during
multi-user boot <br>
time? <br>
<br>
</blockquote>
Same error. I tried to remove if_iwm.ko from /boot/kernel and
boot )) <br>
</blockquote>
<br>
iwm(4) is likely compiled into the kernel... forgive me. You can
proabbly <br>
try <br>
hint.iwm.disabled="1" <br>
or <br>
hint.iwm.0.disabled="1" <br>
<br>
in loader.conf and see if that helps or compile a kernel without
iwm <br>
and iwmfw to test. <br>
</blockquote>
Ok, boot with iwm disabled:<br>
<br>
<span style="font-family:monospace"><span
style="color:#000000;background-color:#ffffff;">root@thinkpad:/
# kldstat -v | grep -e 'iw[ml]' </span><br>
26 1 0xffffffff83b3f000 88070 if_iwlwifi.ko
(/boot/kernel/if_iwlwifi.ko) <br>
526 pci/lkpi_iwl_hw_card_ids<br>
<br>
</span>pciconf -lBbcevV:<br>
<br>
<span style="font-family:monospace"><span
style="color:#000000;background-color:#ffffff;">none3@pci0:0:20:3:
class=0x028000 rev=0x30 hdr=0x00 vendor=0x8086
device=0x9df0 subvendor=0x8086 subdevice=0x0034 </span><br>
vendor = 'Intel Corporation' <br>
device = 'Cannon Point-LP CNVi [Wireless-AC]' <br>
class = network <br>
bar [10] = type Memory, range 64, base 0xdd638000, size
16384, disabled <br>
cap 01[c8] = powerspec 3 supports D0 D3 current D3 <br>
cap 05[d0] = MSI supports 1 message, 64 bit <br>
cap 10[40] = PCI-Express 2 root endpoint max data 128(128) FLR
RO NS <br>
max read 128 <br>
cap 11[80] = MSI-X supports 16 messages <br>
Table in map 0x10[0x2000], PBA in map 0x10[0x3000]
<br>
ecap 0000[100] = unknown 0 <br>
ecap 0018[14c] = LTR 1 <br>
ecap 000b[164] = Vendor [1] ID 0010 Rev 0 Length 20<br>
<br>
</span>Attach iwlwifi:<br>
<br>
<span style="font-family:monospace"><span
style="color:#000000;background-color:#ffffff;">root@thinkpad:/
# devctl set driver pci0:0:20:3 iwlwifi </span><br>
devctl: Failed to set pci0:0:20:3 driver to iwlwifi: Input/output
error<br>
<br>
dmesg -a:<br>
</span><br>
<span style="font-family:monospace"><span
style="font-family:monospace"><span
style="color:#000000;background-color:#ffffff;">iwlwifi0:
<iwlwifi> mem 0xdd638000-0xdd63bfff at device 20.3 on
pci0 </span><br>
iwlwifi0: HW_REV=0xFFFFFFFF, PCI issues? <br>
device_attach: iwlwifi0 attach returned 5<br>
<br>
</span></span><br>
</body>
</html>
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?89fa7191-30aa-e550-0e5d-d061c985c5ab>