From: Ping-Ke Shih <pkshih@realtek.com>
To: Abdurrahman Karadag <abdurrahmankaradag19@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"rtl8821cerfe2@gmail.com" <rtl8821cerfe2@gmail.com>
Subject: RE: [PATCH rtw-next 2/2] wifi: rtw88: pci: warn when a TX ring stops advancing
Date: Mon, 5 Oct 2026 01:52:04 +0000 [thread overview]
Message-ID: <afa2a308990349fb9ad41f6a5031508f@realtek.com> (raw)
In-Reply-To: <20261002231013.11792-3-abdurrahmankaradag19@gmail.com>
Abdurrahman Karadag <abdurrahmankaradag19@gmail.com> wrote:
> On RTL8821CE the hardware read index of a TX ring can stop moving while
> the driver keeps submitting descriptors. The link stays associated and
> RX keeps working, so from userspace this is a dead network with no
> explanation: ping and curl report 100% loss and nothing appears in the
> log.
>
> A watchdog dumping the TXBD registers caught five of these across three
> boots, all with station power save off and REG_TXPAUSE at 0x00.
As you mentioned, REG_TXPAUSE at 0xff sometimes. I think it will be
a right direction to dig why it becomes 0xff. Then, we don't need
a watchdog to detect the status periodically.
next prev parent reply other threads:[~2026-10-05 1:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 23:10 [PATCH rtw-next 0/2] rtw88: recover a stopped TX queue, and notice a stalled ring Abdurrahman Karadag
2026-10-02 23:10 ` [PATCH rtw-next 1/2] wifi: rtw88: pci: wake the TX queues when the rings are reset Abdurrahman Karadag
2026-10-05 1:49 ` Ping-Ke Shih
2026-10-02 23:10 ` [PATCH rtw-next 2/2] wifi: rtw88: pci: warn when a TX ring stops advancing Abdurrahman Karadag
2026-10-05 1:52 ` Ping-Ke Shih [this message]
2026-10-02 23:37 ` [PATCH rtw-next 0/2] rtw88: recover a stopped TX queue, and notice a stalled ring Abdurrahman Karadag
2026-10-05 1:44 ` 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=afa2a308990349fb9ad41f6a5031508f@realtek.com \
--to=pkshih@realtek.com \
--cc=abdurrahmankaradag19@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rtl8821cerfe2@gmail.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 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.