Received: by 2002:a05:6a11:4021:0:0:0:0 with SMTP id ky33csp2108669pxb; Fri, 17 Sep 2021 02:20:18 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwawqi1Lsyh6Z4qJj1dE4ohPL7mEgy0JYKYQgiMAmNvuee4CLnJGvq3GVwBSxnlkVVaVpXL X-Received: by 2002:a50:bf42:: with SMTP id g2mr5772086edk.299.1631870418791; Fri, 17 Sep 2021 02:20:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1631870418; cv=none; d=google.com; s=arc-20160816; b=bP1Et+zgVgMwVFgu510ZdyUv2XREYrlkOVoHT9+ppFNM1zPQAZAMMqx8ODNWElH0Ar RJ6Zvi2IELNGSkiO//XWAWT9il+wwBejadHDQugAytCPoBoczky2KEjJ22JEviLDVkpp yu//DqiODLkXgjm9H3vo+iKZ0Th28MWf4ieTpVFSVB3iPHOM6qsMCg/Q8QqNSZzyxHQk C1aTQ8EtUVnZe4wcx3xC5kzv9kIm424sHwsngyL9AAWNvoQ+HkfQEN23cw1th7IHOKLR /MV1XyXllN3dWW0GpIPBTR9mzQpHEJD+EvEnLffdxcepVdYwOdpZ/oYioIqP0AE0Fwsh f4PA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:organization:references:in-reply-to:date:cc:to:from :subject:message-id; bh=jri3OismLw2yVYKDFGSCfh/Pnm5CZYGKgo1DaBMRtWw=; b=X5WozZDJnhoThi1WgBbg9/EsyCLhhzYcsz01B7Ub1gehW3VscZOwbj51a7T9vXGPdq qgSnz8GtbNXq8K2iExDvqln8mAHkAjB3VQCfsO56wr4XeelJYAtotz2Hp7RRjN2eyyXs fM0yX+ZPtHNjRh6UwBbqfuaYXxgEOaoEMa/Y+Z2aSK8xokByolOFOiSQXI4EzfizgHTF aotByCXVNE1b2eZDu5d+RbYVDTow3H4BLdYHqeK+ojmCe3z6WhCSbkx+LdTr82ZuOakw zQLW1/t+jch1pdtOxCDZVFoZr+EhCIvtDvUoIY/sPxdllEFKMtetWWte10EcT+xeHaHV f0Mg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id d10si7517883edm.434.2021.09.17.02.19.17; Fri, 17 Sep 2021 02:20:18 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239350AbhIPVrg (ORCPT + 99 others); Thu, 16 Sep 2021 17:47:36 -0400 Received: from mga17.intel.com ([192.55.52.151]:38014 "EHLO mga17.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234847AbhIPVrf (ORCPT ); Thu, 16 Sep 2021 17:47:35 -0400 X-IronPort-AV: E=McAfee;i="6200,9189,10109"; a="202826894" X-IronPort-AV: E=Sophos;i="5.85,299,1624345200"; d="scan'208";a="202826894" Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 16 Sep 2021 14:46:14 -0700 X-IronPort-AV: E=Sophos;i="5.85,299,1624345200"; d="scan'208";a="699151007" Received: from cjoseph-mobl.amr.corp.intel.com ([10.252.131.10]) by fmsmga006-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 16 Sep 2021 14:46:13 -0700 Message-ID: Subject: Re: Intel bt broken on linux-next? From: Tedd Ho-Jeong An To: Jakub Kicinski , linux-bluetooth@vger.kernel.org Cc: Marcel Holtmann , Johan Hedberg , Luiz Augusto von Dentz Date: Thu, 16 Sep 2021 14:46:13 -0700 In-Reply-To: <20210916132747.218fb12f@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> References: <20210916132747.218fb12f@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> Organization: Intel Corporation Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.36.5 (3.36.5-2.fc32) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-bluetooth@vger.kernel.org Hi Jakub On Thu, 2021-09-16 at 13:27 -0700, Jakub Kicinski wrote: > Hi, > > looks like my Bluetooth stopped working after upgrade to linux-next > as of yesterday (next-20210915). Is this a known problem? > > [ 19.594522] Bluetooth: hci0: Bootloader revision 0.1 build 42 week 52 2015 > [ 19.595515] Bluetooth: hci0: Device revision is 2 > [ 19.595517] Bluetooth: hci0: Secure boot is enabled > [ 19.595517] Bluetooth: hci0: OTP lock is enabled > [ 19.595518] Bluetooth: hci0: API lock is enabled > [ 19.595519] Bluetooth: hci0: Debug lock is disabled > [ 19.595520] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 > [ 19.661829] Bluetooth: hci0: Found device firmware: intel/ibt-17-16-1.sfi > [ 19.661924] Bluetooth: hci0: Boot Address: 0x40800 > [ 19.661925] Bluetooth: hci0: Firmware Version: 6-12.21 > [ 21.971023] Bluetooth: hci0: command 0xfc09 tx timeout > [ 29.970995] Bluetooth: hci0: Failed to send firmware data (-110) > [ 29.971108] Bluetooth: hci0: sending frame failed (-19) > [ 29.971119] Bluetooth: hci0: Intel reset sent to retry FW download > [ 30.123040] Bluetooth: hci0: sending frame failed (-19) > [ 32.097392] Bluetooth: hci0: command 0xfc1e tx timeout > [ 32.097408] Bluetooth: hci0: Failed to read MSFT supported features (-110) > > I think it's part of: > > 00:14.3 Network controller: Intel Corporation Cannon Point-LP CNVi [Wireless-AC] (rev 30) I don't think it was known issue to me. What was your previous kernel before switching to next-20210915? Also, do you still have a problem after cold reboot the system? (completely shutdown and wait some seconds before start). From the log above, the command (0xfc09) is failing which the device may in the weird state. Regards, Tedd