On 08/04/2026 17:26, Bitterblue Smith wrote:
> On 31/03/2026 03:32, Ping-Ke Shih wrote:
>>
>> LB F <goainwo@gmail.com> wrote:
>>>
>>> Could you advise on how to investigate this further? For example:
>>>
>>>   - Is there a debug flag or register dump we could capture right
>>>     before the first corrupted frame in a burst?
>>>   - Would it help to log C2H (chip-to-host) traffic around the
>>>     time of these events?
>>
>> I have never heard about this symptom from internal, so no clear
>> idea for that. Sorry.
>>
>>>
>>> I am ready to run any specific tests you need. In the meantime,
>>> I agree that filtering by DRV_INFO_SIZE is the right practical
>>> solution, and I'm waiting for your official patch to test locally.
>>
>> As malformed frames happen randomly, more validations like
>> DRV_INFO_SIZE are needed. I think Bitterblue is working on the
>> test patch. :)
>>
>> Ping-Ke
>>
> 
> Yes, I am preparing a patch now.

Here is the patch, finally.