From: Kalle Valo <kvalo@kernel.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: "Jeff Johnson" <quic_jjohnson@quicinc.com>,
"François Armand" <fanf42@gmail.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux ath11k" <ath11k@lists.infradead.org>,
"Linux Bluetooth" <linux-bluetooth@vger.kernel.org>
Subject: Re: Fwd: Qualcomm NFA725A on T14s AMD Gen3: Bluetooth: hci0: Failed to send headers (or body or access otp area)
Date: Mon, 21 Aug 2023 08:02:18 +0300 [thread overview]
Message-ID: <87il99j8dh.fsf@kernel.org> (raw)
In-Reply-To: <a669d2d5-fee8-5841-eb5f-b7d047d3cdb2@gmail.com> (Bagas Sanjaya's message of "Fri, 18 Aug 2023 17:16:17 +0700")
Bagas Sanjaya <bagasdotme@gmail.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).
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@kernel.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: "Jeff Johnson" <quic_jjohnson@quicinc.com>,
"François Armand" <fanf42@gmail.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux ath11k" <ath11k@lists.infradead.org>,
"Linux Bluetooth" <linux-bluetooth@vger.kernel.org>
Subject: Re: Fwd: Qualcomm NFA725A on T14s AMD Gen3: Bluetooth: hci0: Failed to send headers (or body or access otp area)
Date: Mon, 21 Aug 2023 08:02:18 +0300 [thread overview]
Message-ID: <87il99j8dh.fsf@kernel.org> (raw)
In-Reply-To: <a669d2d5-fee8-5841-eb5f-b7d047d3cdb2@gmail.com> (Bagas Sanjaya's message of "Fri, 18 Aug 2023 17:16:17 +0700")
Bagas Sanjaya <bagasdotme@gmail.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).
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-08-21 5:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 10:16 Fwd: Qualcomm NFA725A on T14s AMD Gen3: Bluetooth: hci0: Failed to send headers (or body or access otp area) Bagas Sanjaya
2023-08-18 10:16 ` Bagas Sanjaya
2023-08-21 5:02 ` Kalle Valo [this message]
2023-08-21 5:02 ` Kalle Valo
2023-08-22 8:21 ` Bagas Sanjaya
2023-08-22 8:21 ` Bagas Sanjaya
2023-08-22 13:01 ` Kalle Valo
2023-08-22 13:01 ` Kalle Valo
2023-08-28 7:08 ` François
2023-08-28 7:08 ` François
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=87il99j8dh.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=bagasdotme@gmail.com \
--cc=fanf42@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_jjohnson@quicinc.com \
/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.