From: Ping-Ke Shih <pkshih@realtek.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ryan@testtoast.com" <ryan@testtoast.com>
Cc: "linux-sunxi@lists.linux.dev" <linux-sunxi@lists.linux.dev>
Subject: Re: [BUG] RTL8821CS panic on entering power-save mode
Date: Fri, 15 Mar 2024 13:47:59 +0000 [thread overview]
Message-ID: <902ff7d3d6221f28df21c2e5b3e743671355c874.camel@realtek.com> (raw)
In-Reply-To: <d5889133-4b8b-49bc-a26f-204ee9fcfdbb@app.fastmail.com>
On Fri, 2024-03-15 at 22:30 +1300, Ryan Walklin wrote:
>
> On Wed, 13 Mar 2024, at 7:05 PM, Ping-Ke Shih wrote:
>
> > Try module parameter rtw_disable_lps_deep_mode=1 to see if it works well.
>
> Adding 'options rtw88_core disable_lps_deep=1' did help significantly, and bluetooth connections
> now seem stable. I still get a lot of
>
> [ 267.074209] rtw_8821cs mmc2:0001:1: timed out to flush queue 1
>
> (1-2 per second every few seconds) in dmesg, particularly during downloads over wifi.
This is because it is trying to enter PS mode but TX queue is still not empty.
If power consumption is not big deal to you, try to turn off PS by
iw wlan0 set power_save off
I think messages can be disappear.
>
> > The IO of SDIO is slower than PCIE, so maybe we can try to enlarge timeout time
> > in rtw_power_mode_change():
>
> This didn't make any change without disabling the power-saving modes, I also tried increasing some
> of the other timeouts without an effect.
>
No idea for now. SDIO looks much different from PCIE.
next prev parent reply other threads:[~2024-03-15 13:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 22:42 [BUG] RTL8821CS panic on entering power-save mode Ryan Walklin
2024-03-13 6:05 ` Ping-Ke Shih
2024-03-13 20:11 ` [BUG] rtw88: RTL8821CS warning " Ryan Walklin
2024-03-15 9:30 ` [BUG] RTL8821CS panic " Ryan Walklin
2024-03-15 13:47 ` Ping-Ke Shih [this message]
2024-03-17 8:40 ` Ryan Walklin
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=902ff7d3d6221f28df21c2e5b3e743671355c874.camel@realtek.com \
--to=pkshih@realtek.com \
--cc=linux-sunxi@lists.linux.dev \
--cc=linux-wireless@vger.kernel.org \
--cc=ryan@testtoast.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