linux-kernel - Re: Fwd: Qualcomm NFA725A on T14s AMD Gen3: Bluetooth: hci0: Failed to send headers (or body or access otp area)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87il99j8dh.fsf@kernel.org>
Date:   Mon, 21 Aug 2023 08:02:18 +0300
From:   Kalle Valo <kvalo@...nel.org>
To:     Bagas Sanjaya <bagasdotme@...il.com>
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>
Subject: Re: Fwd: Qualcomm NFA725A on T14s AMD Gen3: Bluetooth: hci0: Failed
 to send headers (or body or access otp area)

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

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

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