From: Abdurrahman Karadag <abdurrahmankaradag19@gmail.com>
To: pkshih@realtek.com
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH rtw-next v2] wifi: rtw88: pci: wake the TX queues when the rings are reset
Date: Fri, 23 Oct 2026 14:18:40 +0300 [thread overview]
Message-ID: <20261023111840.2844381-1-abdurrahmankaradag19@gmail.com> (raw)
In-Reply-To: <74b5ab33c8a3445ea45d2f5d0c8d7387@realtek.com>
> I meant if you have more dumps in the future, please analyze them and
> give us summary.
Understood. One result since that mail, since it closes the observation
I said I could not place: on a healthy link HISR0 carries the same
unmasked bits while interrupts keep being delivered and the BE ring was
empty at every sample. So those bits are set in normal operation and do
not hold off the edge-triggered interrupt. Not a lead.
> Let's me clarify two groups are:
> 1. stalled TX ring causing queue_stopped flag raised
> 2. link (connection) loss (not clear yet)
Group 2 as you put it. Group 1 with one qualification: the raised flag
is a later stage of that group rather than the whole of it. Most of the
stalled-ring captures were taken while the ring was still filling and
the flag was not set yet; it was set in a minority, where the ring had
reached the stop threshold. So the patch covers the end state of group
1, not group 1.
prev parent reply other threads:[~2026-10-23 11:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-10 19:31 Abdurrahman Karadag
2026-10-12 6:57 ` Ping-Ke Shih
2026-10-13 22:08 ` Abdurrahman Karadag
2026-10-14 1:52 ` Ping-Ke Shih
2026-10-16 22:47 ` Abdurrahman Karadag
2026-10-19 1:25 ` Ping-Ke Shih
2026-10-21 10:13 ` Abdurrahman Karadag
2026-10-22 3:49 ` Ping-Ke Shih
2026-10-23 11:18 ` Abdurrahman Karadag [this message]
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=20261023111840.2844381-1-abdurrahmankaradag19@gmail.com \
--to=abdurrahmankaradag19@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
all inboxes | Powered by JetHome®