From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 203535] Bluetooth: command tx timeout with Intel Corporation Wireless 7260 in A2DP mode
Date: Sat, 02 Jan 2021 07:19:14 +0000 [thread overview]
Message-ID: <bug-203535-62941-dP5K2T9023@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203535-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=203535
--- Comment #10 from Leonid Kalmaev (kalmaevlv@gmail.com) ---
(In reply to ValdikSS from comment #9)
> It's been 12 days without any issues.
>
> Workaround this bug by executing the following command, which disables
> Bluetooth autosuspend:
>
> echo 'options btusb enable_autosuspend=0' | sudo tee
> /etc/modprobe.d/bluetooth.conf
>
> Reboot afterwards.
Hi. This does not work for some reason in the case of sleep. After waking up
from sleep in powertop I see a good state again. Can you advise on more options
for this to work correctly?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2021-01-02 7:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 0:23 [Bug 203535] New: Bluetooth: command tx timeout with Intel Corporation Wireless 7260 in A2DP mode bugzilla-daemon
2020-04-05 15:53 ` [Bug 203535] " bugzilla-daemon
2020-04-05 15:54 ` bugzilla-daemon
2020-05-25 10:30 ` bugzilla-daemon
2020-07-06 20:53 ` bugzilla-daemon
2020-10-03 8:28 ` bugzilla-daemon
2020-12-12 14:56 ` bugzilla-daemon
2020-12-14 20:15 ` bugzilla-daemon
2020-12-26 17:19 ` bugzilla-daemon
2021-01-02 7:19 ` bugzilla-daemon [this message]
2021-01-14 16:59 ` bugzilla-daemon
2022-11-30 17:35 ` bugzilla-daemon
2023-03-12 20:21 ` bugzilla-daemon
2023-03-23 0:08 ` bugzilla-daemon
2023-04-22 15:59 ` 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-203535-62941-dP5K2T9023@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.