From: John Salamon <salamonj9@gmail.com>
To: pkshih@realtek.com
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: PROBLEM: RTL8821CS SDIO card is unusable on boot (Anbernic RG353V)
Date: Tue, 26 Sep 2023 11:36:43 +0930 [thread overview]
Message-ID: <CA+fyA4SqT4jgpWeq_ipp7i3ZM7s=gQkSdtsPw6x+zeJdGcXvqw@mail.gmail.com> (raw)
On an Anbernic RG353V using the latest mainline kernel, the wifi
(RTL8821CS) is in an unusable state on boot (no wireless adapter
available) and I get the following kernel messages:
[ 5.878711] rtw_8821cs mmc3:0001:1: Firmware version 24.11.0, H2C version 12
[ 6.218709] rtw_8821cs mmc3:0001:1: sdio read32 failed (0x11080): -110
[ 6.218844] rtw_8821cs mmc3:0001:1: sdio write32 failed (0x11080): -110
[ 6.219136] rtw_8821cs mmc3:0001:1: sdio read32 failed (0x10080): -110
[ 6.219230] rtw_8821cs mmc3:0001:1: sdio write32 failed (0x10080): -110
[ 6.219409] rtw_8821cs mmc3:0001:1: sdio read32 failed (0x10040): -110
[ 6.219503] rtw_8821cs mmc3:0001:1: sdio write32 failed (0x10040): -110
[ 6.219706] rtw_8821cs mmc3:0001:1: sdio read32 failed (0x11700): -110
[ 6.219800] rtw_8821cs mmc3:0001:1: sdio write32 failed (0x11700): -110
[ 6.219967] rtw_8821cs mmc3:0001:1: sdio read32 failed (0x11708): -110
[ 6.220474] rtw_8821cs mmc3:0001:1: sdio write32 failed (0x11330): -110
[ 6.220673] rtw_8821cs mmc3:0001:1: sdio read32 failed (0x1022c): -110
[ 6.220863] rtw_8821cs mmc3:0001:1: sdio write32 failed (0x1022c): -110
[ 6.220993] rtw_8821cs mmc3:0001:1: sdio read32 failed (0x20): -110
[ 6.221570] rtw_8821cs mmc3:0001:1: sdio read32 failed (0x11208): -110
[ 6.221695] rtw_8821cs mmc3:0001:1: sdio write32 failed (0x11208): -110
[ 6.222076] rtw_8821cs mmc3:0001:1: sdio read32 failed (0x20): -110
[ 6.222195] rtw_8821cs mmc3:0001:1: sdio read32 failed (0x24): -110
[ 6.222322] rtw_8821cs mmc3:0001:1: sdio read32 failed (0x28): -110
[ 6.222471] rtw_8821cs mmc3:0001:1: Failed to write 4608 byte(s) to
SDIO port 0x0000840c
[ 6.222510] rtw_8821cs mmc3:0001:1: failed to write data to rsvd page
[ 6.222680] rtw_8821cs mmc3:0001:1: failed to download rsvd page
[ 6.222851] rtw_8821cs mmc3:0001:1: failed to download firmware
[ 6.223011] rtw_8821cs mmc3:0001:1: failed to setup chip efuse info
[ 6.223033] rtw_8821cs mmc3:0001:1: failed to setup chip information
[ 6.224013] rtw_8821cs: probe of mmc3:0001:1 failed with error -110
If I rmmod rtw_8821cs and modprobe rtw_8821cs, it actually becomes
usable, at least for a while.
After some time, many repeated messages like this appear:
[ 1562.774009] rtw_8821cs mmc3:0001:1: timed out to flush queue 2
[ 1563.234018] rtw_8821cs mmc3:0001:1: timed out to flush queue 1
And I have to do the rmmod/modprobe trick again for it to start working again.
I can always reproduce this on boot.
I am using the latest mainline kernel, uboot and linux-firmware (I've
also tried 6.5 kernel with the same result).
kernel .config:
https://github.com/human9/rg353v_linux/blob/main/linux_new.config
dmesg: https://github.com/human9/rg353v_linux/blob/main/dmesg.txt
reply other threads:[~2023-09-26 2:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CA+fyA4SqT4jgpWeq_ipp7i3ZM7s=gQkSdtsPw6x+zeJdGcXvqw@mail.gmail.com' \
--to=salamonj9@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@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;
as well as URLs for NNTP newsgroup(s).