[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <89c53213-cb9b-7a8c-bc9c-92cabfdbba4d@gmail.com>
Date: Tue, 22 Aug 2023 15:21:13 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: Kalle Valo <kvalo@...nel.org>
Cc: Jeff Johnson <quic_jjohnson@...cinc.com>,
François Armand <fanf42@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux ath11k <ath11k@...ts.infradead.org>,
Linux Bluetooth <linux-bluetooth@...r.kernel.org>,
Marcel Holtmann <marcel@...tmann.org>,
Johan Hedberg <johan.hedberg@...il.com>,
Luiz Augusto von Dentz <luiz.dentz@...il.com>
Subject: Re: Fwd: Qualcomm NFA725A on T14s AMD Gen3: Bluetooth: hci0: Failed
to send headers (or body or access otp area)
On 21/08/2023 12:02, Kalle Valo wrote:
> Bagas Sanjaya <bagasdotme@...il.com> writes:
>
>> Hi,
>>
>> I notice a bug report on Bugzilla [1]. Quoting from it:
>>
>>> Hello,
>>>
>>> (Sorry by advance if it's not the correct place to discuss that, but
>>> I tried other place like my distro kernel forum
>>> (https://bbs.archlinux.org/viewtopic.php?id=286929), interactive
>>> chat, etc and nobody was able to help).
>>>
>>> [1] == Short summary ==
>>>
>>> I have a lenovo T14S AMD Gen 3 with a *Qualcomm NFA725A* Wi-Fi card
>>> (which is actually reported by lspci as QCNFA765) and bluetooth
>>> never worked on it, failing to load the rampatch with "failed to
>>> send header" or "failed to send body" or "Failed to access otp area
>>> (-71)".
>>>
>>> Other people reports bluetooth as working
>>> (https://wiki.archlinux.org/title/Lenovo_ThinkPad_T14s_(AMD)_Gen_3)
>>> and a work friend has a T16 AMD gen1 which seems to have exactly the
>>> same chipset and work flowlessly. So perhaps it's an hardware issue,
>>> but I don't know how to qualify it if so.
>>>
>>> => How can this be further qualified/debuged/workarounded?
>>>
>>> Any help, even RTFM pointing to corresponding manuals would be very
>>> much appreciated.
>
> This looks like a bluetooth bug so not related to ath11k (which is a
> Wi-Fi driver).
>
Oops, I really can't guess which driver is the culprit in this case unless
the reporter also attaches lsmod output. To François: Can you show
lsmod list as requested?
Also Cc: bluetooth people.
--
An old man doll... just what I always wanted! - Clara
Powered by blists - more mailing lists