archive mirror
 help / color / mirror / Atom feed
From: Fernando Ramos <>
To: Takashi Iwai <>
Cc: Paul Menzel <>,
	Marcel Holtmann <>,
	Johan Hedberg <>,
	Luiz Augusto von Dentz <>,
	Tedd Ho-Jeong An <>,,
Subject: Re: [PATCH] Bluetooth: Apply initial command workaround for more Intel chips
Date: Sun, 5 Dec 2021 11:33:04 +0100	[thread overview]
Message-ID: <YayVYIAi56097Ltl@zacax395.localdomain> (raw)
In-Reply-To: <>

On 21/12/02 05:47PM, Takashi Iwai wrote:
> Thanks, so this seems depending on the hardware, maybe a subtle
> difference matters.  As far as I read the code changes, the workaround
> was applied in the past unconditionally, so it must be fairly safe
> even if the chip works as is.
> Or, for avoiding the unnecessarily application of the workaround,
> should it be changed as a fallback after the failure at the first
> try...?

I don't know if this helps, but I started experiencing this same issue ("hci0:
command 0xfc05 tx timeout") yesterday after a kernel upgrade.

My controller is a different one:

    8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter

I tried with different (older) versions of the v5.15.x kernel but none worked.

Now, this is the interesting (?) part: today, when I switched on the computer
to keep testing, the bluetooth was *already* working once again.

I have reviewed my bash history to try to figure out what is it that I did, and
the only thing I see is that yesterday, before going to sleep, I did a full
poweroff instead of a reset (which is what I used yesterday to try different

This does not make any sense... but then I found this [1] post from someone else
who experienced the same.

Is there any reasonable explanation for this? Could this be the reason why you
seem to have different results with the same controller (8087:0a2a)?


  parent reply	other threads:[~2021-12-05 10:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-02 16:22 [PATCH] Bluetooth: Apply initial command workaround for more Intel chips Takashi Iwai
2021-12-02 16:32 ` Paul Menzel
2021-12-02 16:47   ` Takashi Iwai
2021-12-02 16:58     ` Paul Menzel
2021-12-03  7:24       ` Takashi Iwai
2021-12-03 21:18         ` Marcel Holtmann
2021-12-04 11:20           ` Takashi Iwai
2021-12-05 10:33     ` Fernando Ramos [this message]
2021-12-07 16:14       ` Marcel Holtmann
2021-12-10 13:23         ` Takashi Iwai
2022-01-16 14:06           ` Paul Menzel
2022-01-20 14:26             ` Thorsten Leemhuis
2022-01-20 15:07               ` Marcel Holtmann
2022-01-20 15:13                 ` Thorsten Leemhuis
2022-01-20 14:32             ` Takashi Iwai
2021-12-28 12:43 ` Thorsten Leemhuis

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YayVYIAi56097Ltl@zacax395.localdomain \ \ \ \ \ \ \ \ \ \

* 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).