Re: [Bug report] rtw89: 8852b: IO_PAGE_FAULTs with beacon filter feature enabled

[Bitterblue Smith]

On 14/05/2025 06:29, Bernie Huang wrote:
> -----Original Message-----
> From: Ping-Ke Shih <pkshih@xxxxxxxxxxx> 
> Sent: Thursday, May 8, 2025 8:59 AM
> To: Fedor Pchelkin <boddah8794@xxxxxxxxx>
> Cc: Bernie Huang <phhuang@xxxxxxxxxxx>; linux-wireless@xxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx
> Subject: RE: [Bug report] rtw89: 8852b: IO_PAGE_FAULTs with beacon filter feature enabled
> 
> Fedor Pchelkin <boddah8794@xxxxxxxxx> wrote:
>>> On Thu, 17. Apr 01:05, Ping-Ke Shih wrote:
>>>> Fedor Pchelkin <boddah8794@xxxxxxxxx> wrote:
>>>>>
>>>>> On Wed, 16. Apr 00:49, Ping-Ke Shih wrote:
>>>>>> As bisection, can I summarize as below table?
>>>>>>
>>>>>>     d56c261e52           firmware             IO_PAGE_FAULT
>>>>>>    (CQM support)
>>>>>>   ---------------      -----------          -----------------
>>>>>>       o                 0.29.29.7                  yes
>>>>>>       o                 0.29.29.5                  no
>>>>>>       x                 0.29.29.7                  no
>>>>>>       x                 0.29.29.5                  no
>>>>>>
>>>>>> If this table is correct, we will check the beacon filter feature in firmware.
>>>>>>
>>>>>
>>>>> Yes, it correctly describes the situation. My suspicion currently 
>>>>> falls on the beacon filter feature in firmware, too.
>>>>
>>>> Could you help to test when we have updated firmware?
>>>>
>>>
>>> Hi,
>>>
>>> Were you able to reproduce or track down the problem?
> 
>> Yes, we have reproduced this problem, and we found sending firmware command during deep PS mode will raise IO_PAGE_FAULT. With below setting to disable deep PS > mode, the symptom can disappear.
> 
>>   rtw89_core.ko disable_ps_mode=y
> 
>> Now we are arranging CAT-C equipment to capture signals in PCIE bus to see what happens at that moment. 
> 
>> One possible solution (workaround) is to avoid sending firmware commands during deep PS mode, before we found out the root cause. 
> 
> Hi Fedor,
> 
> Could you please check whether the attached firmware fixes this issue?
> The firmware version should be 1.29.29.9.
By the way, what does the first number mean? The previous version was
0.29.29.8. I would expect only the last number to change for this bug fix.