From owner-freebsd-wireless@freebsd.org Thu Mar 30 03:15:28 2017 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CDA77D25E72 for ; Thu, 30 Mar 2017 03:15:28 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (unknown [IPv6:2607:f2f8:a098::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A04871BD2 for ; Thu, 30 Mar 2017 03:15:28 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [IPv6:2605:e000:1313:b3:223:24ff:fea8:4fb5] (2605:e000:1313:b3:223:24ff:fea8:4fb5 [IPv6:2605:e000:1313:b3:223:24ff:fea8:4fb5]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id e74cde88 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO for ; Wed, 29 Mar 2017 20:15:27 -0700 (PDT) To: freebsd-wireless@freebsd.org From: Pete Wright Subject: iwm Intel 3165 Message-ID: <5b648cbd-c546-aa14-f69a-d08c9973c1d2@nomadlogic.org> Date: Wed, 29 Mar 2017 20:14:54 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Mar 2017 03:15:28 -0000 Hi there, I have a new laptop with the following Intel wireless chipset that seems to be having problems getting enabled: iwm0@pci0:1:0:0: class=0x028000 card=0x44108086 chip=0x31658086 rev=0x79 hdr=0x00 vendor = 'Intel Corporation' device = 'Wireless 3165' class = network I have the following configured in my loader.conf: if_iwm_load="YES" iwm3160fw_load="YES" iwm7260fw_load="YES" iwm7265fw_load="YES" iwm8000Cfw_load="YES" I have seen the following error on both the latest 12-CURRENT snapshot as well as the drm-next branch that work is being done on to support newer Intel graphics and can reproduce on both code bases. Here is what I'm seeing in the dmesg buffer: iwm0: mem 0xd1000000-0xd1001fff at device 0.0 on pci1 iwm7265Dfw: root not mounted yet, no way to load image iwm0: could not read firmware iwm7265Dfw (error 0) iwm0: dumping device error log iwm0: Invalid error log pointer 0x00000000 iwm0: driver status: iwm0: tx ring 0: qid=0 cur=0 queued=0 iwm0: tx ring 1: qid=1 cur=0 queued=0 iwm0: tx ring 2: qid=2 cur=0 queued=0 iwm0: tx ring 3: qid=3 cur=0 queued=0 uhub0: iwm0: tx ring 4: qid=4 cur=0 queued=0 iwm0: tx ring 5: qid=5 cur=0 queued=0 iwm0: tx ring 6: qid=6 cur=0 queued=0 iwm0: tx ring 7: qid=7 cur=0 queued=0 iwm0: tx ring 8: qid=8 cur=0 queued=0 iwm0: tx ring 9: qid=9 cur=0 queued=0 iwm0: tx ring 10: qid=10 cur=0 queued=0 iwm0: tx ring 11: qid=11 cur=0 queued=0 iwm0: tx ring 12: qid=12 cur=0 queued=0 iwm0: tx ring 13: qid=13 cur=0 queued=0 iwm0: tx ring 14: qid=14 cur=0 queued=0 iwm0: tx ring 15: qid=15 cur=0 queued=0 iwm0: tx ring 16: qid=16 cur=0 queued=0 iwm0: tx ring 17: qid=17 cur=0 queued=0 iwm0: tx ring 18: qid=18 cur=0 queued=0 iwm0: tx ring 19: qid=19 cur=0 queued=0 iwm0: tx ring 20: qid=20 cur=0 queued=0 iwm0: tx ring 21: qid=21 cur=0 queued=0 iwm0: tx ring 22: qid=22 cur=0 queued=0 iwm0: tx ring 23: qid=23 cur=0 queued=0 iwm0: tx ring 24: qid=24 cur=0 queued=0 iwm0: tx ring 25: qid=25 cur=0 queued=0 iwm0: tx ring 26: qid=26 cur=0 queued=0 iwm0: tx ring 27: qid=27 cur=0 queued=0 iwm0: tx ring 28: qid=28 cur=0 queued=0 iwm0: tx ring 29: qid=29 cur=0 queued=0 iwm0: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 iwm0: rx ring: cur=0 iwm0: 802.11 state -1 iwm_intr: null vap iwm0: Failed to start INIT ucode: 35 When i try to configure the device the netif rc script errors out stating the device doesn't exist. Let me know if any additional debugging info would be helpful, and if this is a real issue I am def willing to help test patches etc. Cheers! -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA