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] hci0: command 0xfc05 tx timeout in kernel 6.7.1
Date: Wed, 12 Jun 2024 01:06:03 +0000	[thread overview]
Message-ID: <bug-218416-62941-2Gi28hPuUU@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218416-62941@https.bugzilla.kernel.org/>

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

--- Comment #35 from Priit O. (priit@ww.ee) ---
And yes, it is regression. also it does not work with kernel 6.6 (LTS).
However it does work perfectly well with kernel 6.1.92.

Linux Zen 6.1.92-1-MANJARO #1 SMP PREEMPT_DYNAMIC Mon May 27 03:37:00 UTC 2024
x86_64 GNU/Linux

$ dmesg | grep -i bluetooth
[    5.621856] Bluetooth: Core ver 2.22
[    5.621877] NET: Registered PF_BLUETOOTH protocol family
[    5.621878] Bluetooth: HCI device and connection manager initialized
[    5.621881] Bluetooth: HCI socket layer initialized
[    5.621883] Bluetooth: L2CAP socket layer initialized
[    5.621887] Bluetooth: SCO socket layer initialized
[    5.659250] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017
[    5.661255] Bluetooth: hci0: Device revision is 1
[    5.661259] Bluetooth: hci0: Secure boot is enabled
[    5.661260] Bluetooth: hci0: OTP lock is enabled
[    5.661262] Bluetooth: hci0: API lock is enabled
[    5.661263] Bluetooth: hci0: Debug lock is disabled
[    5.661264] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[    5.663789] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[    5.663805] Bluetooth: hci0: Boot Address: 0x24800
[    5.663807] Bluetooth: hci0: Firmware Version: 132-3.24
[    6.464952] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    6.464954] Bluetooth: BNEP filters: protocol multicast
[    6.464957] Bluetooth: BNEP socket layer initialized
[    7.025995] Bluetooth: hci0: Waiting for firmware download to complete
[    7.026211] Bluetooth: hci0: Firmware loaded in 1330487 usecs
[    7.026245] Bluetooth: hci0: Waiting for device to boot
[    7.041215] Bluetooth: hci0: Device booted in 14630 usecs
[    7.041217] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
[    7.041527] Bluetooth: hci0: Found Intel DDC parameters:
intel/ibt-20-1-3.ddc
[    7.047218] Bluetooth: hci0: Applying Intel DDC parameters completed
[    7.050221] Bluetooth: hci0: Firmware revision 0.3 build 132 week 3 2024
[    7.217324] Bluetooth: MGMT ver 1.22
[   18.841731] Bluetooth: RFCOMM TTY layer initialized
[   18.841737] Bluetooth: RFCOMM socket layer initialized
[   18.841740] Bluetooth: RFCOMM ver 1.11

sorry, but I have no time or will to install and test with every non-supported
kernel versions inbetween 6.1 and 6.6 to see where the error came back in.

-- 
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:[~2024-06-12  1:06 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-24 14:29 [Bug 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
2024-01-24 23:39 ` [Bug 218416] " 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 [this message]
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-2Gi28hPuUU@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).