linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 203535] New: Bluetooth: command tx timeout with Intel Corporation Wireless 7260 in A2DP mode
Date: Tue, 07 May 2019 00:23:59 +0000	[thread overview]
Message-ID: <bug-203535-62941@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 203535
           Summary: Bluetooth: command tx timeout with Intel Corporation
                    Wireless 7260 in A2DP mode
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.0.11
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Bluetooth
          Assignee: linux-bluetooth@vger.kernel.org
          Reporter: iam@valdikss.org.ru
        Regression: No

I have Intel Corporation Wireless 7260 (rev 73) with 8087:07dc Intel Corp.
Bluetooth module.
From time to time, pausing and playing audio over A2DP causes Bluetooth stack
to stall with the following in kernel log:

Bluetooth: hci0: command 0x041f tx timeout
Bluetooth: hci0: command 0x0406 tx timeout
Bluetooth: hci0: command 0x0c03 tx timeout
Bluetooth: hci0: HCI reset during shutdown failed
Bluetooth: hci0: urb 0000000044e22bee failed to resubmit (113)
Bluetooth: hci0: urb 00000000fc976241 failed to resubmit (113)
Bluetooth: hci0: urb 00000000a59b126a failed to resubmit (113)
Bluetooth: hci0: urb 00000000215e997b failed to resubmit (113)

Note that "HCI reset during shutdown failed" happened when I tried to disable
Bluetooth and enable it again.
Removing btusb and btintel modules and inserting them again helps.

Bluetooth: hci0: read Intel version: 370710018002030d57
Bluetooth: hci0: Intel device is already patched. patch num: 57

Kernel version: 5.0.11. Happened on 4.9-4.19 as well.
Fedora's firmware package: linux-firmware.noarch 20190416-95.fc30

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

             reply	other threads:[~2019-05-07  0:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-07  0:23 bugzilla-daemon [this message]
2020-04-05 15:53 ` [Bug 203535] Bluetooth: command tx timeout with Intel Corporation Wireless 7260 in A2DP mode 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
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@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).