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, 12 Dec 2020 14:56:52 +0000 [thread overview]
Message-ID: <bug-203535-62941-8jSaprdUgx@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203535-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=203535
Leonid Kalmaev (kalmaevlv@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kalmaevlv@gmail.com
--- Comment #7 from Leonid Kalmaev (kalmaevlv@gmail.com) ---
hi, i am seeing the same problem. I think the reason is the automatic saving of
energy.
In my case, if you use the powertop tool and carefully look at the Tunables
tab, you can find Autosuspend for unknown USB device 1-1.3 (8087: 07dc)
change the state to bad and the problem no longer persists until the next
system reboot.
uname -a
Linux dns-book 5.8.0-33-generic #36~20.04.1-Ubuntu SMP Wed Dec 9 17:01:13 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
lspci
07:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)
lsusb
Bus 001 Device 003: ID 8087:07dc Intel Corp.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2020-12-12 14:58 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 [this message]
2020-12-14 20:15 ` bugzilla-daemon
2020-12-26 17:19 ` bugzilla-daemon
2021-01-02 7:19 ` bugzilla-daemon
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-8jSaprdUgx@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 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).