From: Ping-Ke Shih <pkshih@realtek.com>
To: Fedor Pchelkin <boddah8794@gmail.com>
Cc: Bernie Huang <phhuang@realtek.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [Bug report] rtw89: 8852b: IO_PAGE_FAULTs with beacon filter feature enabled
Date: Thu, 8 May 2025 00:59:28 +0000 [thread overview]
Message-ID: <419811cccd774d38b5a9c0bbcdf5dfbe@realtek.com> (raw)
In-Reply-To: <7injzacfmvhrugcovyxkn4elnaxnzg27c26zmcqzrwhottyk7e@ap5ellaozcg4>
Fedor Pchelkin <boddah8794@gmail.com> wrote:
> On Thu, 17. Apr 01:05, Ping-Ke Shih wrote:
> > Fedor Pchelkin <boddah8794@gmail.com> 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.
next prev parent reply other threads:[~2025-05-08 0:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 10:23 [Bug report] rtw89: 8852b: IO_PAGE_FAULTs with beacon filter feature enabled Fedor Pchelkin
2025-04-16 0:49 ` Ping-Ke Shih
2025-04-16 10:57 ` Fedor Pchelkin
2025-04-17 1:05 ` Ping-Ke Shih
2025-04-17 8:39 ` Fedor Pchelkin
2025-05-07 15:25 ` Fedor Pchelkin
2025-05-08 0:59 ` Ping-Ke Shih [this message]
2025-05-14 3:29 ` Bernie Huang
2025-05-15 21:11 ` Fedor Pchelkin
2025-06-23 17:22 ` Bitterblue Smith
2025-06-24 0:14 ` Ping-Ke Shih
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=419811cccd774d38b5a9c0bbcdf5dfbe@realtek.com \
--to=pkshih@realtek.com \
--cc=boddah8794@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=phhuang@realtek.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox