Received: by 2002:ac0:a582:0:0:0:0:0 with SMTP id m2-v6csp165264imm; Fri, 5 Oct 2018 01:31:21 -0700 (PDT) X-Google-Smtp-Source: ACcGV62m+QAqLsyFjQTMFT2VTqYzfC9Erf1DFNOshxTRa+Y81LUP9m/KqdTbl2SFQ4Jehko5CNfN X-Received: by 2002:a63:7e1c:: with SMTP id z28-v6mr9228893pgc.190.1538728281167; Fri, 05 Oct 2018 01:31:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1538728281; cv=none; d=google.com; s=arc-20160816; b=YLnszGgRapGRgXvG2wylTLOms0oL4z6+R8FdxY1teKzq+GxP4jS46XHXI9Ae6zGjdf 56oA8uCPOFnOg9Nrj+g+ZVVHgZKp/XgXY901Qjs3yFfksYCiEGaBPGN7nP7IYYLAa6y6 9MakswucF3XYND1gr33oE1/pNNNOYubkm00WsTq81dM5Hxgw8BX2c75bW/FQbWlRFH03 apU3IGJ9wSYOsf+qG7fNhUF/XDxzB0Xy0t/PDI3x2oAv3gtn/+4Cj3cmSaGurct6MtXr z+H0YW+0vjBZTB3Qltl5jSYJf6IuiHhUPkwYnPtR8bh6ewR0KoyTPbucA7RJ9YMxclTd lAXQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:to:references:message-id :content-transfer-encoding:cc:date:in-reply-to:from:subject :mime-version; bh=a59RTmXQ95DS54ehu4LV/PgUDkNPi6nqFvxnXGCp/aI=; b=Lgk5LDlqnypQCA4ydV6KjFLcjPfJJLblFABNZ6DhbT0ts0lSttqCXicNUph+femRDz 96E6ICylnZO/+X11Et11BCGXDPENjaJn5+n7QcJQ3ZXeltbsPRMHyetjse18EdIIXiuj DYH7SsxH5S+gzvQEOiIyCJNXZxDODvpnN9weWYzYBY6tqotR7UVdhxBEj+Cfka0aSl7n XoXJmeakJm8jkBJXPNa1nEtwnDIrKlHxoUSuFFASDb3XK51nzjLmwOQmF+WFdWbOSWWu nrpXM3R5NkRiRl4f0ouGZLgvgfPygfeARARrgslB5QCzvbDGb2Un2HtZq0O7d51NZoq4 5A/w== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=canonical.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v67-v6si8124604pfk.264.2018.10.05.01.31.05; Fri, 05 Oct 2018 01:31:21 -0700 (PDT) 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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=canonical.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728395AbeJEP23 convert rfc822-to-8bit (ORCPT + 99 others); Fri, 5 Oct 2018 11:28:29 -0400 Received: from youngberry.canonical.com ([91.189.89.112]:33986 "EHLO youngberry.canonical.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727236AbeJEP23 (ORCPT ); Fri, 5 Oct 2018 11:28:29 -0400 Received: from mail-pf1-f198.google.com ([209.85.210.198]) by youngberry.canonical.com with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.76) (envelope-from ) id 1g8LVY-0005oq-8J for linux-kernel@vger.kernel.org; Fri, 05 Oct 2018 08:30:48 +0000 Received: by mail-pf1-f198.google.com with SMTP id k1-v6so6073626pfg.13 for ; Fri, 05 Oct 2018 01:30:48 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=G0wX4OWQOKY8mwxXK2Npgsg3zBYShCED/kWqHiDPWPA=; b=KY94lWHJt6RRPMGQTdU8pE/qA1DzxTXAhP1m0vIAUqLhBJBDQUdy7Sw/RQcgqW6iG3 +9oSbkcTbUSaHyedQQr0k86hgZQgfFJ0CMRb10AYvxStT73Uc+0Bp72HI+to5Apq6gUh 4bPQ35byS96ahIbvM8X8tceAl9FnRTQZN9nUCEYB1g4FKBKnHYFLqpMuPpk6In7hKRwe Gr0HnZmAfYX4vj4udztGxqNjCc7AOcQo8q2dI0f82qigYr4qayXx4owFFOD/6qTVGAQt 1ajcwWtEgIHsXmovlwxRKGSyGnu2J1OX+Zpu5wgbygVVT0afD+Q6HQje5SAt5/zIoaCy NqPw== X-Gm-Message-State: ABuFfohO1KcMzzZNNfIsnvV0GMPbOqk4yFVIhHumPoKfbImyV5DgME9L XfDIQzkkDuS3ooR27tn18n3yooMwfDFpc02xYzMdLBJqg20063e9SIj3RGACWM+OOLulJAfCU7K PncRAG+F4xlFZrPE+55KDJsjg1qTJg8v2D369wubOIQ== X-Received: by 2002:a63:82c6:: with SMTP id w189-v6mr9143754pgd.211.1538728246800; Fri, 05 Oct 2018 01:30:46 -0700 (PDT) X-Received: by 2002:a63:82c6:: with SMTP id w189-v6mr9143735pgd.211.1538728246468; Fri, 05 Oct 2018 01:30:46 -0700 (PDT) Received: from [10.101.46.95] (61-220-137-37.HINET-IP.hinet.net. [61.220.137.37]) by smtp.gmail.com with ESMTPSA id g65-v6sm12768098pfg.98.2018.10.05.01.30.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 05 Oct 2018 01:30:45 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\)) Subject: Re: [PATCH 3/3] iwlwifi: Load firmware exclusively for Intel WiFi From: Kai Heng Feng In-Reply-To: <910F8A29-3141-422F-87EE-7BFBCDE9060C@holtmann.org> Date: Fri, 5 Oct 2018 16:30:41 +0800 Cc: Matt Chen , Luciano Coelho , LKML , Johannes Berg , "Grumbach, Emmanuel" , linuxwifi@intel.com, Kalle Valo , "David S. Miller" , linux-wireless , netdev@vger.kernel.org Content-Transfer-Encoding: 8BIT Message-Id: References: <20181003071513.13004-3-kai.heng.feng@canonical.com> <2787bccf20b6f647de9f4cafae5fd223e771b167.camel@intel.com> <81B978A9-270E-4C0B-BE67-D05899B1BC3B@canonical.com> <24BAAAAB-17E4-4820-A09A-50984B8EBA40@canonical.com> <910F8A29-3141-422F-87EE-7BFBCDE9060C@holtmann.org> To: Marcel Holtmann X-Mailer: Apple Mail (2.3445.100.39) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Marcel, > On Oct 4, 2018, at 2:25 AM, Marcel Holtmann wrote: > > Hi Kai-Heng, > >>> I think Canonical were facing some wifi fw load error from some 8260 >>> earlier module during the BT still loading the fw. >>> I believe we had later 8260 sku that fixed this issue. >> >> But there are already 8260 that is affected by this bug in the wild. >> >> Search "Bluetooth: hci0: Failed to send firmware data (-38)” and there are lots of user are affected. > > which SKUs are these actually. What are the initial details about the boot loader. For the Bluetooth side, you should be able to grab them from dmesg or by running btmon. Here’s the dmesg | grep Bluetooth: [ 6.086600] Bluetooth: Core ver 2.22 [ 6.086618] Bluetooth: HCI device and connection manager initialized [ 6.086621] Bluetooth: HCI socket layer initialized [ 6.086625] Bluetooth: L2CAP socket layer initialized [ 6.086632] Bluetooth: SCO socket layer initialized [ 6.107794] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [ 6.112803] Bluetooth: hci0: Device revision is 5 [ 6.112805] Bluetooth: hci0: Secure boot is enabled [ 6.112805] Bluetooth: hci0: OTP lock is enabled [ 6.112806] Bluetooth: hci0: API lock is enabled [ 6.112807] Bluetooth: hci0: Debug lock is disabled [ 6.112808] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 6.115231] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [ 6.210353] Bluetooth: hci0: Failed to send firmware data (-38) [ 8.153357] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 8.153358] Bluetooth: BNEP filters: protocol multicast [ 8.153362] Bluetooth: BNEP socket layer initialized [ 13.563790] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [ 13.568806] Bluetooth: hci0: Device revision is 5 [ 13.568808] Bluetooth: hci0: Secure boot is enabled [ 13.568809] Bluetooth: hci0: OTP lock is enabled [ 13.568810] Bluetooth: hci0: API lock is enabled [ 13.568811] Bluetooth: hci0: Debug lock is disabled [ 13.568813] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 13.569072] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [ 15.220327] Bluetooth: hci0: Waiting for firmware download to complete [ 15.220805] Bluetooth: hci0: Firmware loaded in 1618764 usecs [ 15.220877] Bluetooth: hci0: Waiting for device to boot [ 15.233031] Bluetooth: hci0: Device booted in 11881 usecs [ 15.233274] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc [ 15.236794] Bluetooth: hci0: Applying Intel DDC parameters completed [ 17.232497] Bluetooth: RFCOMM TTY layer initialized [ 17.232505] Bluetooth: RFCOMM socket layer initialized [ 17.232510] Bluetooth: RFCOMM ver 1.11 I’ll file a Bugzilla if we need full dmesg as attachment. > > So I am not in favor of this kind of hack and creating dependencies between drivers. If you only have a hammer, then everything looks like a nail. And this is a massive hammer trying to squash everything. This problem needs to be debugged. And this starts by providing affected SKU information and firmware information. So get the details about the SKU and its Bluetooth and WiFi boot loaders. Apology for the hammer approach, which is the best way I can think of. Of course it’s much better if we can solve this without the ugly hack. Kai-Heng > > Regards > > Marcel >