From: Tedd Ho-Jeong An <tedd.an@linux.intel.com>
To: Jakub Kicinski <kuba@kernel.org>, linux-bluetooth@vger.kernel.org
Cc: Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Subject: Re: Intel bt broken on linux-next?
Date: Thu, 16 Sep 2021 14:46:13 -0700 [thread overview]
Message-ID: <ae7804e8a9877f94a7c798ac4c787a7f7f7f21af.camel@linux.intel.com> (raw)
In-Reply-To: <20210916132747.218fb12f@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
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
next prev parent reply other threads:[~2021-09-16 21:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 20:27 Intel bt broken on linux-next? Jakub Kicinski
2021-09-16 21:46 ` Tedd Ho-Jeong An [this message]
2021-09-16 21:56 ` Jakub Kicinski
2021-09-21 23:00 ` Jakub Kicinski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ae7804e8a9877f94a7c798ac4c787a7f7f7f21af.camel@linux.intel.com \
--to=tedd.an@linux.intel.com \
--cc=johan.hedberg@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox