All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Wren Turkal <wt@penguintechs.org>
Cc: ath11k@lists.infradead.org,  linux-bluetooth@vger.kernel.org
Subject: Re: QCA6390 bluetooth doesn't work after warm boot or disable/reenable
Date: Mon, 08 Apr 2024 08:22:51 +0300	[thread overview]
Message-ID: <87sezwjums.fsf@kernel.org> (raw)
In-Reply-To: <1b3d3937-6679-491e-a5c6-818ae8ac639a@penguintechs.org> (Wren Turkal's message of "Sat, 6 Apr 2024 13:27:56 -0700")

Wren Turkal <wt@penguintechs.org> writes:

>>> Apr 04 10:15:06 braindead.localdomain kernel: Bluetooth: hci0: QCA
>>> Failed to send TLV segment (-110)
>>> Apr 04 10:15:06 braindead.localdomain kernel: Bluetooth: hci0: QCA
>>> Failed to download patch (-110)
>> Logs are mostly unchanges when restarting the bluetooth service
>> after a cold boot with the bluetooth originally working.
>> 
>>> FWIW, I get similar logs after logging into KDE Plasma. I also get
>>> similar logs after a warm boot.
>>>
>>> This appears to be some kind of bug in the initialization of the
>>> hardware. Is there any additional information I can provide to help
>>> troubleshoot this problem.
>> I will also say that the bluetooth appears to work throught a
>> suspend/resume cycle as long as I don't restart the bluetooth
>> service.
>> Oh, and my laptop is a Dell 9310 if that helps.
>
> Kalle, I noticed that you reported having a Dell 9310 in 2021 in a
> message on this very mailing list. Do you happen to still have that
> laptop? If so, so you still test on that laptop at all? I am curious
> if it is having the same issue I am experiencing?

Yes, I still have that laptop and I use it as my daily driver. But I
don't use Bluetooth and I don't even have the Bluetooth enabled in my
.config.

BTW ath11k is a Wi-Fi driver so most likely it isn't affecting your
problem.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches


  parent reply	other threads:[~2024-04-08  5:23 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-04 19:14 QCA6390 bluetooth doesn't work after warm boot or disable/reenable Wren Turkal
2024-04-05  5:30 ` Wren Turkal
2024-04-06 20:16 ` Wren Turkal
2024-04-06 20:27   ` Wren Turkal
2024-04-06 20:29     ` Wren Turkal
2024-04-06 20:50       ` Wren Turkal
2024-04-08  5:22     ` Kalle Valo [this message]
2024-04-08 18:35       ` Wren Turkal
2024-04-10  7:21         ` Kalle Valo
2024-04-08 19:49     ` Wren Turkal
2024-04-09 19:53       ` Wren Turkal
2024-04-09 20:02         ` Wren Turkal
2024-04-09 20:03         ` Luiz Augusto von Dentz
2024-04-09 20:09           ` Wren Turkal
2024-04-09 20:11           ` Wren Turkal
2024-04-10 22:00             ` Wren Turkal
2024-04-10 22:40               ` Wren Turkal
2024-04-11 20:30                 ` Wren Turkal
2024-04-12 19:46                   ` Wren Turkal
2024-04-14 12:04                     ` quic_zijuhu
2024-04-15  7:52                       ` Wren Turkal
2024-04-15  8:07                         ` quic_zijuhu
2024-04-15  8:51                           ` Wren Turkal
2024-04-15  9:29                             ` quic_zijuhu
2024-04-15 11:34                             ` quic_zijuhu

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=87sezwjums.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=ath11k@lists.infradead.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=wt@penguintechs.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.