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: Wed, 15 Jun 2022 10:12:44 +0000	[thread overview]
Message-ID: <bug-215167-62941-6otTn4D8R1@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 #37 from Ievgen Popovych (jmennius@gmail.com) ---
So I was trying to reproduce, kept the trace running for a few days or more,
but then it never happened and I've stopped tracing.
Now it happened again, on Fedora kernel 5.17.11, when waking up from suspend.
As I am looking though the logs there were total of 4 occurrences of "Reading
Intel version command failed", but I think only today I've noticed BT not
working and having to do the rmmod dance (few times to fix it).

> Jun 15 10:19:54 ievgen-xps kernel: Bluetooth: hci0: Opcode 0x c01 failed:
> -110
> Jun 15 10:19:54 ievgen-xps kernel: Bluetooth: hci0: command 0x0c01 tx timeout
> Jun 15 10:19:56 ievgen-xps systemd-sleep[311042]: System returned from sleep
> state.
> Jun 15 10:19:56 ievgen-xps bluetoothd[876]: Controller resume with wake event
> 0x0
> Jun 15 10:19:56 ievgen-xps kernel: Bluetooth: hci0: command 0x0c1a tx timeout
> Jun 15 10:19:56 ievgen-xps kernel: Bluetooth: hci0: Opcode 0x c1a failed:
> -110
> Jun 15 10:19:56 ievgen-xps kernel: PM: suspend exit
> Jun 15 10:19:56 ievgen-xps systemd[1]: Starting systemd-rfkill.service -
> Load/Save RF Kill Switch Status...
> Jun 15 10:19:56 ievgen-xps systemd[1]: Stopped target bluetooth.target -
> Bluetooth Support.
> Jun 15 10:19:56 ievgen-xps systemd[1665]: Stopped target bluetooth.target -
> Bluetooth.
> Jun 15 10:19:56 ievgen-xps systemd[1]: Started systemd-rfkill.service -
> Load/Save RF Kill Switch Status.
> Jun 15 10:19:56 ievgen-xps kernel: usb 1-4: new full-speed USB device number
> 39 using xhci_hcd
> Jun 15 10:19:56 ievgen-xps kernel: usb 1-4: New USB device found,
> idVendor=8087, idProduct=0029, bcdDevice= 0.01
> Jun 15 10:19:56 ievgen-xps kernel: usb 1-4: New USB device strings: Mfr=0,
> Product=0, SerialNumber=0
> Jun 15 10:19:56 ievgen-xps upowerd[902]: treating change event as add on
> /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4
> Jun 15 10:19:56 ievgen-xps systemd[1]: Reached target bluetooth.target -
> Bluetooth Support.
> Jun 15 10:19:56 ievgen-xps systemd[1665]: Reached target bluetooth.target -
> Bluetooth.
...
> Jun 15 10:19:58 ievgen-xps kernel: Bluetooth: hci0: command 0xfc05 tx timeout
> Jun 15 10:19:58 ievgen-xps kernel: Bluetooth: hci0: Reading Intel version
> command failed (-110)

-- 
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:[~2022-06-15 10:12 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 [this message]
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
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-6otTn4D8R1@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).