Date: Fri, 1 Apr 2022 11:53:57 +0000 (UTC) From: "Bjoern A. Zeeb" <bz@FreeBSD.org> To: Oleksandr Kryvulia <shuriku@shurik.kiev.ua> Cc: FreeBSD wireless mailing list <wireless@freebsd.org> Subject: Re: iwlwifi failed to attach Message-ID: <alpine.BSF.2.00.2204011137300.68830@ai.fobar.qr> In-Reply-To: <2c64cf74-ec67-5e6d-e36d-df1bb2c5a402@shurik.kiev.ua> 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> <89fa7191-30aa-e550-0e5d-d061c985c5ab@shurik.kiev.ua> <alpine.BSF.2.00.2204010044480.68830@ai.fobar.qr> <2c64cf74-ec67-5e6d-e36d-df1bb2c5a402@shurik.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-566494758-1648814038=:68830 Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8BIT On Fri, 1 Apr 2022, Oleksandr Kryvulia wrote: > 01.04.22 03:59, Bjoern A. Zeeb пишет: >> Sorry, I think I have to roll this back. >> >> I assume you are on GENERIC? > Yes, GENERIC-NODEBUG. >> >> I assume iwm(4) normally is loaded as a module along with firmware >> and works fine? > Yes, iwm(4) works fine, I'm sending this message over it. >> >> Ignoring the above hint.iwm... if you move if_iwm.ko out of >> /boot/kernel temporary and run kldxref /boot/kernel and reboot >> on a recent main or stable/13, what happens without you doing any >> devctl? Is iwlfiwi auto-loaded? does pciconf show the BAR enabled >> then? > > # mv /boot/kernel/if_iwm.ko /home/o.kryvulia/ > # kldxref /boot/kernel > # shutdown -p now > > Power on and boot: > > Autoloading module: if_iwlwifi > Intel(R) Wireless WiFi based driver for FreeBSD > Autoloading module: ig4 > Autoloading module: pchtherm > pchtherm0: <CannonLake-LP Thermal Subsystem> mem 0xdd643000-0xdd643fff at > device 18.0 on pci0 > iwlwifi0: <iwlwifi> mem 0xdd638000-0xdd63bfff at device 20.3 on pci0 > iwlwifi0: HW_REV=0xFFFFFFFF, PCI issues? > device_attach: iwlwifi0 attach returned 5 > > pciconf shows the same: > > 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 Okay, can I ask you for one last test. Can you boot -s (to single user) and check the full pciconf there and then simply exit and let to boot continue back to iwm. You may need to mount -uw / in order to save the full pciconf output. iwlwifi tends to disable resources on detach, so we could se an aftermath problem here even on attach failure. I just want to make sure given the device is in D3 that we do boot up and are good before any wifi driver attaches. Later, Bjoern -- Bjoern A. Zeeb r15:7 --0-566494758-1648814038=:68830--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.2204011137300.68830>