Received: by 2002:a05:6a11:4021:0:0:0:0 with SMTP id ky33csp2119264pxb; Fri, 17 Sep 2021 02:38:44 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxdLTf/h+UDY2Xj/0rWbEs/fRYM8V8wKqwQiE2+fg6Kj6WinNyWa/b9R1s2FMFPzmHm3lDG X-Received: by 2002:a05:6638:1909:: with SMTP id p9mr8117501jal.108.1631871524723; Fri, 17 Sep 2021 02:38:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1631871524; cv=none; d=google.com; s=arc-20160816; b=h5+mJeiIzHqct9iZ8F33v9E5aOCeeUajlWRojeYe3mPVpQRiPewSfGZk65JfiYmYAm 7/KEMcAvIVrQWYjoC+JDOoesb6HDpe3RAlpCWTZ7zi++dquf8OMrwqKJ9WUOb0ItcI03 Go1DfIrnfZfeMz5Ikym9t/tNNqbgNCERCkwvTAUUFbYUx1KEWNSVkmU5v1B3wEZDGp99 VQiZSH3p2wm0uC4Yiy/M5wmtF2OqE+c67SW8QhikMW/MMClK1gWziJ67Q32eLTOTEFaw h7SqTdqs7Q7ygftY1w8SD1XfPeGmrwkvKlmz2x2vYulPTA4xuRhtlGtN6ZWTqZ3VGSLb J2+A== 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 :references:in-reply-to:message-id:subject:cc:to:from:date :dkim-signature; bh=ETgmo3H5uwVToSwvjLDIOzOpGYVxO9nKpZvo7dAW1lw=; b=z4Y70bj59opx/0B5orcfx7uCJBGOVDfBCEHACR5Eukl0gI4Na6h6xxvbLGPpLZbawQ 3Ur2s5Jf1oV6th3G4/SLP74qkYUC3ITiFb+HfaAScSorSgtdQZyqpS/JfujwWHpwyMPE fgiMSvu7wbx5ZJwwsY5xPmrlqa9ddxOF+bEIIVsKH5gD4K/CJYz5XFDT/MTMn32WJwJe Ho19f1EqrwcTdAxuSSOJ+rpuPaevlmc6A8JaCNNEy+x3v5oBbJjIdutWvMrI13GWxmWQ kgYcP9HBU950DW0601dSZeyXxmabmnBa4kMLSXEt08lDuYtT9CnRBFXuPlbmwoI1K/zr Fl5Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=GYAKiL9A; 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=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id g2si5810870jat.51.2021.09.17.02.38.18; Fri, 17 Sep 2021 02:38:44 -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; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=GYAKiL9A; 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=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237460AbhIPV5r (ORCPT + 99 others); Thu, 16 Sep 2021 17:57:47 -0400 Received: from mail.kernel.org ([198.145.29.99]:53468 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234142AbhIPV5r (ORCPT ); Thu, 16 Sep 2021 17:57:47 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 445F861074; Thu, 16 Sep 2021 21:56:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1631829386; bh=KqcwjMSbYMAR0WEwC7rc9H2/fH2JYcnSySalojHI2s8=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=GYAKiL9AXWsjfc4KK/mv+LhMr9K+MeXxcID0ZGH0gEpcTDCQRLGN8FXJfCZ6hBba9 y22LP+aQQwuJ8XdpbzGtCef34GrQu1R6LrQBWWMLO25szksQOeQs+XJTkMOicDSv6K AscvhFdlC5crsYEeL9W0e81LQW32SOGpR1wcnMdez0HrSlgCShVGMM7jfGzKjoXR6l m/5yFyvCcnx4GLS4mBgDWIPhY2iaZTpRLSI5cXIlmoywpNC6zRUCnebtKiNzR5yCs5 F3TeQZ1OLb7cIXljHx83Hx+8tyO7SqqHImuyyWy/NzlYlt33h1AzbmWyzNwd/RmDHi 3VfTp577mF20g== Date: Thu, 16 Sep 2021 14:56:25 -0700 From: Jakub Kicinski To: Tedd Ho-Jeong An Cc: linux-bluetooth@vger.kernel.org, Marcel Holtmann , Johan Hedberg , Luiz Augusto von Dentz Subject: Re: Intel bt broken on linux-next? Message-ID: <20210916145625.4e0b8c8e@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> In-Reply-To: References: <20210916132747.218fb12f@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-bluetooth@vger.kernel.org On Thu, 16 Sep 2021 14:46:13 -0700 Tedd Ho-Jeong An wrote: > > 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? v5.14.3 > Also, do you still have a problem after cold reboot the system? (completely shutdown and wait some > seconds before start). Let me get back to you on that. Thanks! > From the log above, the command (0xfc09) is failing which the device may in the weird state.