mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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>
Subject: RE: [PATCH rtw-next v2] wifi: rtw88: pci: wake the TX queues when the rings are reset
Date: Thu, 22 Oct 2026 03:49:01 +0000	[thread overview]
Message-ID: <74b5ab33c8a3445ea45d2f5d0c8d7387@realtek.com> (raw)
In-Reply-To: <20261021101356.1976617-1-abdurrahmankaradag19@gmail.com>

Abdurrahman Karadag <abdurrahmankaradag19@gmail.com> wrote:
> > I need your help to summarize the dumps. I don't have much time to
> > analyze them. Sorry.

I meant if you have more dumps in the future, please analyze them and
give us summary.

> They fall into two main groups: stalled TX rings, and a dead link
> despite continuing ring progress. In the first the hardware read index
> stops advancing while the ring fills behind it, and in a couple it had
> filled and the queue was stopped - the state v4 clears. In this group
> recovery was observed only after reconnect or interface down/up. The
> second group is the larger one and I have nothing for it; that is what
> the monitor capture would be for. The patch does not claim to address
> every link loss.

Let's me clarify two groups are:

1. stalled TX ring causing queue_stopped flag raised
2. link (connection) loss (not clear yet)

Ping-Ke


      reply	other threads:[~2026-10-22  3:49 UTC|newest]

Thread overview: 8+ 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 [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=74b5ab33c8a3445ea45d2f5d0c8d7387@realtek.com \
    --to=pkshih@realtek.com \
    --cc=abdurrahmankaradag19@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@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 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®