Re: QCA6390 broken in current kernel

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2024/8/1 15:53, Wren Turkal wrote:
> Zijun,
> 
> On 7/30/24 6:28 PM, Zijun Hu wrote:
>> On 2024/7/31 04:12, Wren Turkal wrote:
>>> Zijun,
>>>
>>> On 7/30/24 12:48 PM, Wren Turkal wrote:
>>>> Zijun,
>>>>
>>>> On 7/30/24 12:26 PM, Wren Turkal wrote:
>>>>> On 7/29/24 9:25 AM, Zijun Hu wrote:
>>>>>> On 2024/7/27 03:25, Wren Turkal wrote:
>>>>>>> On 7/26/24 11:52 AM, Wren Turkal wrote:
>>>>>>>> On 7/25/24 1:47 PM, Wren Turkal wrote:
>>>>>>>>> On 7/25/24 1:35 PM, Luiz Augusto von Dentz wrote:
>>>>>>>>>> Hi Wren,
>>>>>>>>>>
>>>>>>>>>> On Thu, Jul 25, 2024 at 2:35 PM Wren Turkal <wt@xxxxxxxxxxxxxxxx>
>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Hello BT folks,
>>>>>>>>>>>
>>>>>>>>>>> Just so y'all know, the QCA6390 bluetooth hardware appears to be
>>>>>>>>>>> broken
>>>>>>>>>>> at least since commit 720261cfc732.
>>>>>>>>>>>
>>>>>>>>>>> The KDE and Gnome bluetooth control panels appear to think
>>>>>>>>>>> there is no
>>>>>>>>>>> bluetooth hardware. Rolling back to 6.10 appear to function.
>>>>>>>>>>>
>>>>>>>>>>> I have a Dell XPS13 9310.
>>>>>>>>>>>
>>>>>>>>>>> I will attempt to capture some kernel logs in a bit.
>>>>>>>>>>
>>>>>>>>>> git show 720261cfc732
>>>>>>>>>> fatal: ambiguous argument '720261cfc732': unknown revision or
>>>>>>>>>> path not
>>>>>>>>>> in the working tree.
>>>>>>>>>
>>>>>>>>> I gave you the sha for the built fedora rawhide kernel package,
>>>>>>>>> not a
>>>>>>>>> mainline sha. Sorry about that. I thought it was a mainline sha.
>>>>>>>>> I am
>>>>>>>>> trying to bisect the problem. Hopefully, I can get a mainline git
>>>>>>>>> sha
>>>>>>>>> for you soon.
>>>>>>>>>
>>>>>>>>> If it helps, the build date of the kernel is 2024-07-19.
>>>>>>>>>
>>>>>>>>> Sorry about the confusion. Hope this helps track down the problem.
>>>>>>>>
>>>>>>>> I have managed to get the following commit id range for the issue:
>>>>>>>> 80ab5445da6235..e2f710f97f35
>>>>>>>
>>>>>>> Narrowed to 80ab5445da6235..586f14a6a182
>>>>>>>
>>>>>> i feel a little sad that QCA6390 of your machine are broken again.
>>>>>> i find out a doubtful point by checking recent changes.
>>>>>>
>>>>>> you maybe have a attempt for below change if you would like to do
>>>>>> that.
>>>>>> https://patchwork.kernel.org/project/bluetooth/patch/20240730-
>>>>>> qca6390_fix-v1-1-e0340a511756@xxxxxxxxxx/
>>>>>>
>>>>>> thanks
>>>>>>
>>>>>>
>>>>>
>>>>> Yeah, I am sad that my bluetooth is broken again as well. I am trying
>>>>> your patch now to see if it gets my hardware working. Will reply back
>>>>> soon.
>>>>>
>>>>> wt
>>>>
>>>> This patch does not fix the problem. The first broken commit is
>>>> 9a15ce685706e73154. This patch effectively reverts only one part of
>>>> that patch.
>>>>
>>>> FTR, I applied this patch on top of the parent commit of the first
>>>> broken commit. I will try it on the tip of mainline as well.
>>>
>>> This patch doesn't appear to apply cleanly to the current tip of
>>> bluetooth-next/master, so I can't really go further in testing it right
>>> now.
>>>
>>
>> my aim is to known which commit cause this issue ASAP since i very care
>> about QCA6390, now i got it, so don't need any further actions any more.
>>
>>> Also, so you know, Bartosz has said that he is aware of the regression
>>> and is working on it.
>>>
>>
>> i did not notice above info before my last reply, i did not see such
>> info in this discussion thread until your reply as well.
>>
>> BTW, you maybe add relevant link if you are referring something from
>> another discussion thread.
> 
> The discussion was in a another branch on this thread. I think I added
> you to the discussion there.
> 

actually, my first reply is earlier than the other branch of this thread
as shown by below link (^^).

https://lore.kernel.org/linux-bluetooth/27e6a6c5-fb63-4219-be0b-eefa2c116e06@xxxxxxxxxxxxxxxx/
2024-07-25 18:34 QCA6390 broken in current kernel Wren Turkal
2024-07-25 20:35 ` Luiz Augusto von Dentz
2024-07-25 20:47   ` Wren Turkal
2024-07-26 18:52     ` Wren Turkal
2024-07-26 19:25       ` Wren Turkal
*2024-07-29 16:25         ` Zijun Hu*
2024-07-30 19:26           ` Wren Turkal
2024-07-30 19:48             ` Wren Turkal
2024-07-30 20:12               ` Wren Turkal
2024-07-31  1:28                 ` Zijun Hu
2024-08-01  7:53                   ` Wren Turkal
*2024-07-30 19:03         ` Wren Turkal*
2024-07-30 19:59           ` Bartosz Golaszewski
2024-07-30 20:05             ` Wren Turkal
2024-07-31  8:51               ` Bartosz Golaszewski
......
>>> Zijun, you should talk the folks at qualcomm and see if there is any
>>> appetite for getting closer to the Linaro folks with regard to this
>>> stuff. You have been very eager to jump in, and I see that Bartosz and
>>> Luis also seem interested in fixing this. I do wonder if there a way to
>>> take advantage of that to build a better working relationship in this
>>> bluetooth space with qualcomm and the linux kernel devs.
>>>
>>
>> you maybe ignore that all my reply come from icloud.com, so you maybe
>> not associate it with qualcomm, it is the first time for icloud.com to
>> join BT relevant discussion. (^^)
> 
> I'm sorry. I didn't realize you weren't associated with Qualcomm here.
> Apologies.
>it is all right (^^).
>>> If qualcomm would be interested in hiring a tech person to help with
>>> this stuff. I am definitely interested in helping in this area.
>>>
>>> Thanks,
>>> wt
>>
> 





[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux