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 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1
Date: Wed, 24 Jan 2024 14:29:28 +0000	[thread overview]
Message-ID: <bug-218416-62941@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 218416
           Summary: hci0: command 0xfc05 tx timeout in kernel 6.7.1
           Product: Drivers
           Version: 2.5
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Bluetooth
          Assignee: linux-bluetooth@vger.kernel.org
          Reporter: nickolas@gupton.xyz
        Regression: No

This issue is still present on kernel 6.7.1 and firmware 20240115. 
Opening a new bug for this as directed in this old bug:
https://bugzilla.kernel.org/show_bug.cgi?id=215167

$ uname -a
Linux andromeda 6.7.1-arch1-1 #1 SMP PREEMPT_DYNAMIC Sun, 21 Jan 2024 22:14:10
+0000 x86_64 GNU/Linux

$ lsusb | grep -i bluetooth
Bus 001 Device 006: ID 8087:0029 Intel Corp. AX200 Bluetooth

$ journalctl -b | egrep -i bluetooth
egrep: warning: egrep is obsolescent; using grep -E
Jan 24 00:20:24 andromeda kernel: Bluetooth: Core ver 2.22
Jan 24 00:20:24 andromeda kernel: NET: Registered PF_BLUETOOTH protocol family
Jan 24 00:20:24 andromeda kernel: Bluetooth: HCI device and connection manager
initialized
Jan 24 00:20:24 andromeda kernel: Bluetooth: HCI socket layer initialized
Jan 24 00:20:24 andromeda kernel: Bluetooth: L2CAP socket layer initialized
Jan 24 00:20:24 andromeda kernel: Bluetooth: SCO socket layer initialized
Jan 24 00:20:25 andromeda systemd[1]: Reached target Bluetooth Support.
Jan 24 00:20:25 andromeda NetworkManager[790]: <info>  [1706077225.3441] Loaded
device plugin: NMBluezManager
(/usr/lib/NetworkManager/1.44.2-3/libnm-device-plugin-bluetooth.so)
Jan 24 00:20:27 andromeda kernel: Bluetooth: hci0: command 0xfc05 tx timeout
Jan 24 00:20:27 andromeda kernel: Bluetooth: hci0: Reading Intel version
command failed (-110)

Not sure what other logs or info you need, but just let me know if it would
help.

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

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

             reply	other threads:[~2024-01-24 14:29 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-24 14:29 bugzilla-daemon [this message]
2024-01-24 23:39 ` [Bug 218416] hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
2024-01-30 14:21 ` bugzilla-daemon
2024-01-30 17:05 ` bugzilla-daemon
2024-02-04 10:31 ` bugzilla-daemon
2024-02-10 23:07 ` bugzilla-daemon
2024-02-11 20:32 ` bugzilla-daemon
2024-02-15 20:43 ` bugzilla-daemon
2024-03-09 16:52 ` bugzilla-daemon
2024-03-25  9:38 ` bugzilla-daemon
2024-03-29  8:52 ` bugzilla-daemon
2024-03-29 16:16 ` bugzilla-daemon
2024-03-29 18:31 ` bugzilla-daemon
2024-03-29 18:33 ` bugzilla-daemon
2024-03-29 20:02 ` bugzilla-daemon
2024-03-30 13:44 ` bugzilla-daemon
2024-04-03 12:32 ` bugzilla-daemon
2024-04-03 18:28 ` bugzilla-daemon
2024-04-04 22:50 ` bugzilla-daemon
2024-04-09 12:18 ` bugzilla-daemon
2024-04-09 13:04 ` bugzilla-daemon
2024-04-09 13:45 ` bugzilla-daemon
2024-04-09 13:46 ` bugzilla-daemon
2024-04-09 14:31 ` bugzilla-daemon
2024-04-09 15:12 ` bugzilla-daemon
2024-04-09 19:57 ` bugzilla-daemon
2024-05-23 14:54 ` bugzilla-daemon
2024-05-24  4:17 ` bugzilla-daemon
2024-05-24 15:29 ` bugzilla-daemon
2024-05-24 20:41 ` bugzilla-daemon
2024-05-24 21:01 ` bugzilla-daemon
2024-05-24 21:03 ` bugzilla-daemon
2024-05-24 21:11 ` bugzilla-daemon
2024-05-24 21:19 ` bugzilla-daemon
2024-05-25  5:22 ` bugzilla-daemon
2024-06-12  0:58 ` bugzilla-daemon
2024-06-12  1:06 ` bugzilla-daemon
2024-06-12 15:25 ` 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-218416-62941@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).