Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp1382087imu; Wed, 9 Jan 2019 17:33:59 -0800 (PST) X-Google-Smtp-Source: ALg8bN7PlUkb8pX5i6QAB1anB00VNT2U3aALjBjy4cAjmLCsGZcYZV0PVW3i+rCSGn81NMTMZWd6 X-Received: by 2002:a65:448a:: with SMTP id l10mr7515858pgq.387.1547084039740; Wed, 09 Jan 2019 17:33:59 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1547084039; cv=none; d=google.com; s=arc-20160816; b=f+AGuR/69RjzVB0vM82MQg1zYXFrm+sGFHOONFppuuvG/d/ikzfU37IQy6j3/nVHMM yYKq+603/4TDayhRlTbznsvOXRmxI+Uc75KZ68kkK5klqO+DIfYxWOoU2uKWFvbtMPqu 8EF9Dy/89cdJctmh6r91WdlxmoQHE620npymw7Hrd8PK0ejaSMc27HUbl38Gb0qG1FpE E5aKArYyChw18Dulf8UTJ7RLDnzigmIBoMGRMsRMPxQmhFWlKJEuwXkfy3BNWtUwI88M 0bLiXLtprWznwbSBAoRtuyAJHnd+j55lBtUQCI/fDllCOLE4j4fe87kT7eeH7KBS5XUV +34A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=XwHAkJ9fISo/ig1npHSkgm+SYvr8cIIkKan1oY0IZZk=; b=EkIKhc8M0SIVYlSnk+ososrdzdYAhGH/0ZRtf68s0IweMlqPzONH2gwZtUGayzg6ZF QYbrw6oX9UzWjEtBotYsjUSXEDWYbv3UTWUXRbqnUdpBzzxCWOK2TRAHCuL8Bk471Zhg N2579pWEvEs/kNH45NELZOm+gXf/QligBM5kGgGjBnVw6pzOhxRdRwBVWycWSq1GcBnd TXpEwZeKoY6nzDgI6ifEwuGoZKpO4uhjqJBgSMv0TnpasLSaGwwFiH3qW5MPx+WF/Jdc Nn94vAv03mtI/TLSd0c9iBzT8n1dBc/aXA4ymI1hV5rWLP1cc6SzHMmzn0p+Gd6gu1bv JlaA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=B8sDaeKK; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f5si7245263plo.422.2019.01.09.17.33.44; Wed, 09 Jan 2019 17:33:59 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=B8sDaeKK; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727083AbfAJB3s (ORCPT + 99 others); Wed, 9 Jan 2019 20:29:48 -0500 Received: from mail-oi1-f194.google.com ([209.85.167.194]:44116 "EHLO mail-oi1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726590AbfAJB3s (ORCPT ); Wed, 9 Jan 2019 20:29:48 -0500 Received: by mail-oi1-f194.google.com with SMTP id m6so7972863oig.11; Wed, 09 Jan 2019 17:29:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=XwHAkJ9fISo/ig1npHSkgm+SYvr8cIIkKan1oY0IZZk=; b=B8sDaeKKSJHzmLwzyl2Cc6//+Vwfw0Kf8yjszSuzeM96L/Al7o7VJFAZBQkghIX1jP gZQrP2/i/ORcXWV3Op1LS9sEejxroVqc6IcxrQa7OdOfwQ8UiQF973xsMru2SuccNdOQ HhJm3e/O1FDbGQdPRju58/gps2b+0CpasuQoDvuYBVHQhmBDFLPx7LmLE4Yu6emv8v+A IhuhnIfVHCwo7/wQ4MA6iJItoxd85iYHPhqVhgZZjIkgPDHHRNExLVV04PPfsVg28BZw ffnFT20KE8K9SMeeKAPTTxu24xcPOOgobPdIRGeRH6oabXzLHCMNBBgUhinBQORBGml4 vrpw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=XwHAkJ9fISo/ig1npHSkgm+SYvr8cIIkKan1oY0IZZk=; b=iz9rmVKNoaGGTNWabYHr0FPocjSSVwp2Yi74hYu1kzgRTh27PsNI9Yzb74usrb+ZM0 mjbb8n9ITbVuEdOUK+Yj4AyhQRz2yHkB2KkdnBH+hc+fyBkIuAiryd+Q9xDyf6tH0WdJ Qt50FLhUZ/pRqnI07iROl9/AyjOq2/LnA/YTMYRIE9+2ykSEzbh7KqmAWRD3ZQZ679va w4Lch8EJ+do4lFvntcPkkae51juNxQhrZ3MUcBOyk0gQDJStjQm/w9DpY1+vBRRUS9oK vRm1Xh5UZ8TieAcqVCCKsYTbCzl2WsQyPdQOEFFz/sFAxQeDHYcJi1yyOjeSXL1rCNgz ioaQ== X-Gm-Message-State: AJcUukeM9e0XjsVXOpewI5a/gpPdrC7ueUoLMl58gj9aG5ESjG+5q8kO 2q7MEjl7yYKe8kWcCi7Dya439/TvJdJFEu7cezg= X-Received: by 2002:aca:38c2:: with SMTP id f185mr5598507oia.26.1547083786537; Wed, 09 Jan 2019 17:29:46 -0800 (PST) MIME-Version: 1.0 References: <20181109000800.15431-1-jprvita@gmail.com> <83CA40B2-1AF3-49FA-9F94-C84A3C916583@holtmann.org> In-Reply-To: From: =?UTF-8?Q?Jo=C3=A3o_Paulo_Rechi_Vita?= Date: Wed, 9 Jan 2019 17:29:10 -0800 Message-ID: Subject: Re: [PATCH 3/3] iwlwifi: Load firmware exclusively for Intel WiFi To: Emmanuel Grumbach Cc: Marcel Holtmann , Kai-Heng Feng , Luca Coelho , Kalle Valo , Emmanuel Grumbach , Johannes Berg , "David S. Miller" , Intel Linux Wireless , linux-wireless , Network Development , LKML , Linux Upstreaming Team , =?UTF-8?Q?Jo=C3=A3o_Paulo_Rechi_Vita?= Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 9, 2019 at 10:39 AM Emmanuel Grumbach wro= te: > > Hello, > > > > > > > > > > > our hardware teams from the Bluetooth and WiFi side really need t= o look at this. > > > > > > Were you able to get attention from the hardware teams with the logs > > > I've provided? Are there any news or an idea of when / if we can > > > expect this to be fixed in firmware? If not, do you have suggestions > > > for an alternative solution? > > > > > > > Sorry to bother you again with this, but I'd really like to figure out > > some way forward here. Did you get any feedback from the hardware > > teams? Otherwise, I understand having an inter-dependency between the > > wifi and bt kernel modules is not desirable, so do you have any > > suggestion on how to solve this without adding this dependency? > > > > Have you tried the update the BT firmware with what is now available in > mainline linux-firmware.git? > I heard that this problem has now been resolved. After you update the > BT firmware, you need a full power cycle. Thanks for the reply. The latest firmware files I see upstream are from commit c34a52ab7d, which are the same I had tested with previously. I'm still able to hit the problem, but after the firmware failed to load the Bluetooth adapter got disconnected from the USB bus and then re-connected. Since the iwlwifi firmware loading routine had already finished at this point, the Bluetooth firmware loaded successfully. I had seen this behavior a few times in my previous test, but not always (for example that behavior did not trigger on the test I had previously shared logs for). So, maybe that is the fix that has been implemented in the firmware? And perhaps some other changes in the kernel where preventing that behavior from triggering all the time? I'm pasting logs bellow where both modules where blacklisted and manually loaded with "modprobe iwlwifi & modprobe btusb": Jan 09 16:54:24 endless kernel: Bluetooth: Core ver 2.22 Jan 09 16:54:24 endless kernel: NET: Registered protocol family 31 Jan 09 16:54:24 endless kernel: Bluetooth: HCI device and connection manager initialized Jan 09 16:54:24 endless kernel: Bluetooth: HCI socket layer initialized Jan 09 16:54:24 endless kernel: Bluetooth: L2CAP socket layer initialized Jan 09 16:54:24 endless kernel: Bluetooth: SCO socket layer initialized Jan 09 16:54:24 endless kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory database Jan 09 16:54:24 endless kernel: cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Jan 09 16:54:24 endless kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 Jan 09 16:54:24 endless kernel: cfg80211: failed to load regulatory.db Jan 09 16:54:24 endless kernel: usbcore: registered new interface driver bt= usb Jan 09 16:54:24 endless kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 Jan 09 16:54:24 endless kernel: Bluetooth: hci0: Device revision is 5 Jan 09 16:54:24 endless kernel: Bluetooth: hci0: Secure boot is enabled Jan 09 16:54:24 endless kernel: Bluetooth: hci0: OTP lock is enabled Jan 09 16:54:24 endless kernel: Bluetooth: hci0: API lock is enabled Jan 09 16:54:24 endless kernel: Bluetooth: hci0: Debug lock is disabled Jan 09 16:54:24 endless kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 Jan 09 16:54:24 endless kernel: Intel(R) Wireless WiFi driver for Linux Jan 09 16:54:24 endless kernel: Copyright(c) 2003- 2015 Intel Corporation Jan 09 16:54:24 endless kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi Jan 09 16:54:25 endless kernel: iwlwifi 0000:01:00.0: loaded firmware version 36.7596afd4.0 op_mode iwlmvm Jan 09 16:54:25 endless kernel: iwlwifi 0000:01:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=3D0x208 Jan 09 16:54:25 endless kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.= 3 Jan 09 16:54:25 endless kernel: Bluetooth: BNEP filters: protocol multicast Jan 09 16:54:25 endless kernel: Bluetooth: BNEP socket layer initialized Jan 09 16:54:25 endless kernel: Bluetooth: hci0: Failed to send firmware data (-38) Jan 09 16:54:25 endless kernel: iwlwifi 0000:01:00.0: base HW address: a4:34:d9:81:bf:a5 Jan 09 16:54:25 endless kernel: ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs' Jan 09 16:54:25 endless kernel: thermal thermal_zone6: failed to read out thermal zone (-61) Jan 09 16:54:25 endless kernel: iwlwifi 0000:01:00.0 wlp1s0: renamed from w= lan0 Jan 09 16:54:25 endless kernel: IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready Jan 09 16:54:25 endless kernel: IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready Jan 09 16:54:25 endless kernel: IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready Jan 09 16:54:31 endless kernel: usb 1-7: USB disconnect, device number 3 Jan 09 16:54:32 endless kernel: usb 1-7: new full-speed USB device number 7 using xhci_hcd Jan 09 16:54:32 endless kernel: usb 1-7: New USB device found, idVendor=3D8087, idProduct=3D0a2b, bcdDevice=3D 0.01 Jan 09 16:54:32 endless kernel: usb 1-7: New USB device strings: Mfr=3D0, Product=3D0, SerialNumber=3D0 Jan 09 16:54:32 endless kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 Jan 09 16:54:32 endless kernel: Bluetooth: hci0: Device revision is 5 Jan 09 16:54:32 endless kernel: Bluetooth: hci0: Secure boot is enabled Jan 09 16:54:32 endless kernel: Bluetooth: hci0: OTP lock is enabled Jan 09 16:54:32 endless kernel: Bluetooth: hci0: API lock is enabled Jan 09 16:54:32 endless kernel: Bluetooth: hci0: Debug lock is disabled Jan 09 16:54:32 endless kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 Jan 09 16:54:32 endless kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi Jan 09 16:54:34 endless kernel: Bluetooth: hci0: Waiting for firmware download to complete Jan 09 16:54:34 endless kernel: Bluetooth: hci0: Firmware loaded in 1820173 usecs Jan 09 16:54:34 endless kernel: Bluetooth: hci0: Waiting for device to boot Jan 09 16:54:34 endless kernel: Bluetooth: hci0: Device booted in 11761 use= cs Jan 09 16:54:34 endless kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc Jan 09 16:54:34 endless kernel: Bluetooth: hci0: Applying Intel DDC parameters completed Jan 09 16:54:34 endless kernel: Bluetooth: RFCOMM TTY layer initialized Jan 09 16:54:34 endless kernel: Bluetooth: RFCOMM socket layer initialized Jan 09 16:54:34 endless kernel: Bluetooth: RFCOMM ver 1.11 -- Jo=C3=A3o Paulo Rechi Vita http://about.me/jprvita