All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 215167] Bluetooth: hci0: command 0xfc05 tx timeout
Date: Sun, 05 Dec 2021 07:05:35 +0000	[thread overview]
Message-ID: <bug-215167-62941-XBh6sjlOas@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215167-62941@https.bugzilla.kernel.org/>

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

Takahide Nojima (nozzy123nozzy@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |nozzy123nozzy@gmail.com

--- Comment #12 from Takahide Nojima (nozzy123nozzy@gmail.com) ---
 For reference purposes only, I will report here about the experience of 
similar problem with my laptop. My laptop  also has the intel AX201 and 
the dimidecode command shows  as below, 
---------------here------------
Handle 0x0011, DMI type 1, 27 bytes
System Information
        Manufacturer: HP
        Product Name: HP EliteBook 830 G7 Notebook PC
        Version:  
        Serial Number: XXXXXX
        UUID: xxx-xxx-xxx-xxx
        Wake-up Type: Power Switch
        SKU Number: 20L69PA#ABJ
        Family: 103C_5336AN HP EliteBook
---------------here-----------

 I checked some kernel versions whether AX201 Bluetooth works or not.

As a result, my situation was a little different,
  1. The AX201 works fine in Linux-5.14.16,Linux-5.15.5,Linux-5.16-rc2 
   and Linux-5.16-rc3.
  2. It doesn't work in Linux-5.15.3 and Linux-5.16-rc1.

 The Debian bug tracker reported a similar problem,
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000403.
According to it, a  commit between 5.15.3 and 5.15.4 can improve 
this problem.

 I'm not sure, but I guess the intel AX201 hardware has some versions, 
and it causes whether the 5.15.5 and 5.16-rc3 works or not, for example.

-- 
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:[~2021-12-05  7:05 UTC|newest]

Thread overview: 50+ 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 [this message]
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
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
2024-05-25  5:11 ` bugzilla-daemon
2024-05-26 19:14 ` 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-XBh6sjlOas@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.