From: Ping-Ke Shih <pkshih@realtek.com>
To: Kalle Valo <kvalo@kernel.org>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
"Larry.Finger@lwfinger.net" <Larry.Finger@lwfinger.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: [PATCH v2] wifi: rtw89: 8852b: adjust quota to avoid SER L1 caused by access null page
Date: Wed, 26 Apr 2023 05:16:41 +0000 [thread overview]
Message-ID: <b1c5e4f89ba843cd958f569547caa8e5@realtek.com> (raw)
In-Reply-To: <87r0s7teik.fsf@kernel.org>
> -----Original Message-----
> From: Kalle Valo <kvalo@kernel.org>
> Sent: Wednesday, April 26, 2023 1:10 PM
> To: Ping-Ke Shih <pkshih@realtek.com>
> Cc: stable@vger.kernel.org; Larry.Finger@lwfinger.net; linux-wireless@vger.kernel.org
> Subject: Re: [PATCH v2] wifi: rtw89: 8852b: adjust quota to avoid SER L1 caused by access null page
>
> Ping-Ke Shih <pkshih@realtek.com> writes:
>
> > Though SER can recover this case, traffic can get stuck for a while. Fix it
> > by adjusting page quota to avoid hardware access null page of CMAC/DMAC.
> >
> > Fixes: a1cb097168fa ("wifi: rtw89: 8852b: configure DLE mem")
> > Fixes: 3e870b481733 ("wifi: rtw89: 8852b: add HFC quota arrays")
> > Cc: stable@vger.kernel.org
> > Tested-by: Larry Finger <Larry.Finger@lwfinger.net>
> > Link: https://github.com/lwfinger/rtw89/issues/226#issuecomment-1520776761
> > Link: https://github.com/lwfinger/rtw89/issues/240
> > Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>
> > ---
> > v2: add Fixes, Cc and Tested-by tags suggested by Larry.
>
> Should this go to wireless tree for v6.4?
>
Yes, please take it to v6.4. People can get stable connection with this fix.
Thank you
Ping-Ke
next prev parent reply other threads:[~2023-04-26 5:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 3:47 [PATCH v2] wifi: rtw89: 8852b: adjust quota to avoid SER L1 caused by access null page Ping-Ke Shih
2023-04-26 5:10 ` Kalle Valo
2023-04-26 5:16 ` Ping-Ke Shih [this message]
2023-04-26 5:41 ` Kalle Valo
2023-04-26 15:08 ` Larry Finger
2023-05-12 8:22 ` Kalle Valo
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=b1c5e4f89ba843cd958f569547caa8e5@realtek.com \
--to=pkshih@realtek.com \
--cc=Larry.Finger@lwfinger.net \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.