From nobody Fri Apr 1 11:53:57 2022 X-Original-To: wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4602519F7D06 for ; Fri, 1 Apr 2022 11:54:02 +0000 (UTC) (envelope-from bz@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4KVJVL162Wz3tZZ; Fri, 1 Apr 2022 11:54:02 +0000 (UTC) (envelope-from bz@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1648814042; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=nuDyRumY5iAmhncCEhep8qF26LIg8TdJxSNBF9WqUSQ=; b=IroZw+u91KSZVBWq5OK3WDbj+v3zDbX3T+O1XQuvk597mWknnvD2CJPjvVElg/34hzyklt +iVsu9qpY3MSJMA2yj+PawHBXrLYlXzPQvOdcrmnCZfPfSTkXVTCyuSk73CmpOhd79N6fh zWy73cuyZWDgPgwxdgse7Y/GqlmFOUr0SIp81y14xFxVQLvgZbYDHl98RP2lGWeaNdYFOa BuyDvcvSE7eFpjwuT/8ZGuh6AlGJl6xgBPpaWJakwlLmdcIzNRkPDD5tuJXwV4ICBYuhay N2lDb1yOVxi2jz3YpI80onhBPnCWugRJen4z21U/ZTCFKeI8TBuS3MSh1/zhoQ== Received: from mx1.sbone.de (mx1.sbone.de [IPv6:2a01:4f8:13b:39f::9f:25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE" (not verified)) (Authenticated sender: bz/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id CBAB42F6CB; Fri, 1 Apr 2022 11:54:01 +0000 (UTC) (envelope-from bz@FreeBSD.org) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 9F7DC8D4A17B; Fri, 1 Apr 2022 11:54:00 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 23875E707C0; Fri, 1 Apr 2022 11:54:00 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id o2W-e3XFjAVV; Fri, 1 Apr 2022 11:53:58 +0000 (UTC) Received: from nv.sbone.de (nv.sbone.de [IPv6:fde9:577b:c1a9:31::2013:138]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 47FB9E707B8; Fri, 1 Apr 2022 11:53:58 +0000 (UTC) Date: Fri, 1 Apr 2022 11:53:57 +0000 (UTC) From: "Bjoern A. Zeeb" To: Oleksandr Kryvulia cc: FreeBSD wireless mailing list Subject: Re: iwlwifi failed to attach In-Reply-To: <2c64cf74-ec67-5e6d-e36d-df1bb2c5a402@shurik.kiev.ua> Message-ID: References: <85f3cdd5-9bcc-426b-55e8-f3964de87c52@shurik.kiev.ua> <87e39641-f6c2-3306-e89d-fe6ba5a8ff39@shurik.kiev.ua> <89fa7191-30aa-e550-0e5d-d061c985c5ab@shurik.kiev.ua> <2c64cf74-ec67-5e6d-e36d-df1bb2c5a402@shurik.kiev.ua> X-OpenPGP-Key-Id: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-566494758-1648814038=:68830" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1648814042; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=nuDyRumY5iAmhncCEhep8qF26LIg8TdJxSNBF9WqUSQ=; b=Kv+RMg4YAFSPoXaWS8XXvZeSDD8PCZ8ofl3/gfavGpVhjYsvGIHlBG5nUQ8OdiYlcURxTa 7mINOHdm2MsOu7/eB6aW/VvepFiMceLTrCcjHXpVZAAk+ip1Ucm1AswCgnX67lk55JPSFU pjB/7OLxorUkq5n/JinIOefpZ1VShwlJSe5rfska3yEyWVkfk7WXsxdhN+xKLT13OGdZ9X ZxEzMgigV/hQaH6CK8wp5y5wNXpH+REkTRpJcTml+RVFDKA6mNncjxHjqt9Vxv4MWZahnw 2QmZpiXiVLJcchVXnhTtE+eOYId2yyvdj+2zZr0m9DFIxBwi07C/JFBQ1uSgAQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1648814042; a=rsa-sha256; cv=none; b=VQqjwtYif+Z4zzEjMW0sL6KNfqoRuLgrjVW2UX6P0vj0z2WQTfxdumysAqgCndTa6oa7o9 f5jwfsX3lkBz4k+JsNj7smToQ1VMkQc974Jm68/II8OsgwgGWOOuIlb6n0/fMrz6uy5a24 oQdyS0a4lZgLeaL+sM5cXVs2awPXGzFwz9JID01xipZA1y0kG+Iz0yNyGSVtSkb7SnPiE3 mUJ38SCg3hLMgAziu3EYxiW8cuvSsSzZsBiv3dvCodTrscPQCyoSGHTTxdVyaJDh6v6bwa qosDn0nQ6VZsrX5ZExMK+Kdz9PdKg3K7opka35ID/BcqNognTOrF35hg+Z0ojg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N 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: mem 0xdd643000-0xdd643fff at > device 18.0 on pci0 > iwlwifi0: 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--