linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 215167] Bluetooth: hci0: command 0xfc05 tx timeout
Date: Sun, 26 Feb 2023 23:59:28 +0000	[thread overview]
Message-ID: <bug-215167-62941-74zOg38pG8@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215167-62941@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=215167

--- Comment #48 from Oleksandr Natalenko (oleksandr@natalenko.name) ---
(In reply to Chaim Eliyah from comment #46)
> | Reloading `btusb` module several times makes it working.
> 
> Any specific steps for this? I have not been able to get it to work. Issue
> persists despite reboots incl. hard power off/on. This happened suddenly.

No specific steps, just `modprobe -r btusb && modprobe btusb`.

I'm not facing the issue regularly, for me it happened only once recently after
I powered off the system completely for a couple of days. The issue does not
occur across reboots or suspends/resumes. It also doesn't occur after each
power off (at least, so far).

I've adopted the patch from c#38 like below just to be on the safe side:

```
commit 2875e3ab82d1777a06a356167c52a745827b2ad1
Author: Oleksandr Natalenko <oleksandr@natalenko.name>
Date:   Sun Feb 26 00:17:09 2023 +0100

    Bluetooth: btusb: work around command 0xfc05 tx timeout

    Instead of realoding `btusb` module to tackle this:

    ```
    Bluetooth: hci0: command 0xfc05 tx timeout
    Bluetooth: hci0: Reading Intel version command failed (-110)
    ```

    increase `btusb_qca_cmd_timeout()` sleep duration while hoping
    for the best.

    This looks like an ugly hack.

    Link: https://bugzilla.kernel.org/show_bug.cgi?id=215167
    Signed-off-by: Oleksandr Natalenko <oleksandr@natalenko.name>

diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index 2ad4efdd9e40..7aff6c468c0d 100644
--- a/drivers/bluetooth/btusb.c
+++ b/drivers/bluetooth/btusb.c
@@ -901,7 +901,7 @@ static void btusb_qca_cmd_timeout(struct hci_dev *hdev)
                }

                gpiod_set_value_cansleep(reset_gpio, 0);
-               msleep(200);
+               usleep_range(USEC_PER_SEC / 2, USEC_PER_SEC);
                gpiod_set_value_cansleep(reset_gpio, 1);

                return;
```

Let me know if you are able to test it.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2023-02-26 23:59 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-215167-62941@https.bugzilla.kernel.org/>
2021-11-29 18:07 ` [Bug 215167] Bluetooth: hci0: command 0xfc05 tx timeout bugzilla-daemon
2021-11-29 21:50 ` bugzilla-daemon
2021-11-29 21:52 ` bugzilla-daemon
2021-11-29 21:54 ` bugzilla-daemon
2021-11-29 21:54 ` bugzilla-daemon
2021-11-29 21:54 ` bugzilla-daemon
2021-11-29 21:58 ` bugzilla-daemon
2021-12-01 14:57 ` bugzilla-daemon
2021-12-05  7:05 ` bugzilla-daemon
2021-12-05  8:08 ` bugzilla-daemon
2021-12-11 12:39 ` bugzilla-daemon
2021-12-13  4:26 ` bugzilla-daemon
2021-12-13  4:26 ` bugzilla-daemon
2021-12-13  8:35 ` bugzilla-daemon
2022-02-09  8:48 ` bugzilla-daemon
2022-02-27 13:55 ` bugzilla-daemon
2022-03-14 11:14 ` bugzilla-daemon
2022-03-14 12:18 ` bugzilla-daemon
2022-03-15 13:54 ` bugzilla-daemon
2022-03-16 15:07 ` bugzilla-daemon
2022-04-06  7:18 ` bugzilla-daemon
2022-04-08 21:40 ` bugzilla-daemon
2022-04-09 22:06 ` bugzilla-daemon
2022-05-25 13:16 ` bugzilla-daemon
2022-05-25 13:44 ` bugzilla-daemon
2022-06-15 10:12 ` bugzilla-daemon
2022-06-15 11:17 ` bugzilla-daemon
2022-06-15 11:43   ` [Bug,215167] " bluez.test.bot
2022-06-30 14:16 ` [Bug 215167] " bugzilla-daemon
2022-08-18 15:03 ` bugzilla-daemon
2022-09-27  2:53 ` bugzilla-daemon
2022-09-29  0:49 ` bugzilla-daemon
2022-12-05 11:36 ` bugzilla-daemon
2022-12-28 15:18 ` bugzilla-daemon
2023-02-25 20:57 ` bugzilla-daemon
2023-02-26 23:14 ` bugzilla-daemon
2023-02-26 23:15 ` bugzilla-daemon
2023-02-26 23:59 ` bugzilla-daemon [this message]
2023-02-27  0:58   ` [Bug,215167] " bluez.test.bot
2023-04-21  7:31 ` [Bug 215167] " bugzilla-daemon
2023-04-29  7:37 ` bugzilla-daemon
2023-05-01  9:02 ` bugzilla-daemon
2023-07-09  6:18 ` bugzilla-daemon
2023-07-09  6:23 ` bugzilla-daemon
2023-09-08 11:59 ` bugzilla-daemon
2024-01-16 17:57 ` bugzilla-daemon
2024-01-17 10:38 ` bugzilla-daemon
2024-01-22 10:19 ` bugzilla-daemon

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=bug-215167-62941-74zOg38pG8@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-bluetooth@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).