From: Bitterblue Smith <rtl8821cerfe2@gmail.com>
To: nurofen55@meta.ua, pkshih@realtek.com
Cc: linux-wireless@vger.kernel.org
Subject: Re:
Date: Tue, 14 Jul 2026 18:23:02 +0300 [thread overview]
Message-ID: <af31a567-ad40-4bbd-85db-4b6242680423@gmail.com> (raw)
In-Reply-To: <44184.185.179.215.97.1784041719.metamail@mail.meta.ua>
On 14/07/2026 18:08, nurofen55@meta.ua wrote:
> Hi Ping-Ke,
> Thank you for the quick and insightful analysis!
> Here are the results from your suggestions:
> 1. Firmware Check:
>
> You were absolutely right. I ran `dmesg | grep -i rtw89` on the 7.1.x kernel, and it confirmed that it is indeed loading the new v2 firmware:
>
> rtw89_8852be 0000:02:00.0: loaded firmware rtw89/rtw8852b_fw-2.bin
>
> Firmware version 0.29.29.18 (9e3d777f)
> 2. Power Save Test:
>
> I identified my interface as wlp2s0 and completely disabled power saving:
>
> sudo iw dev wlp2s0 set power_save off
>
> Unfortunately, this did not improve the 2.4GHz stability; the intermittent packet loss and high latency spikes still persist under the same conditions.
> 3. Testing Nearby the AP:
>
> Moving the laptop closer to the router (stronger signal) slightly mitigates the frequency of the drops, but the latency spikes still occur randomly on 2.4GHz, whereas 5GHz remains flawlessly stable.
> Since I am on openSUSE Tumbleweed (a rolling release distribution) and use it for my daily hospital workflow, compiling a custom kernel to manually apply patch 63ccdfac8677 is quite problematic for me at the moment.
> Given that commit 63ccdfac8677 fixes the exact AMPDU drop logic bug introduced in 7.0, it sounds like the perfect candidate to resolve this. Could you please queue this fix for inclusion into the upstream 7.1.x stable kernel tree? Once it is merged there, the openSUSE maintainers will pull it automatically, and I will gladly test the updated repository kernel to confirm the fix!
> Best regards,
>
> Svyatoslav
>
>
Hi,
That patch is already queued for 7.1:
https://lore.kernel.org/stable/20260712105304.agent5-0001@kernel.org/
next prev parent reply other threads:[~2026-07-14 15:23 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 15:08 nurofen55
2026-07-14 15:23 ` Bitterblue Smith [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-09-27 16:50 Rajat Jain
2016-09-27 16:57 ` Rajat Jain
[not found] <CA+yqC4Y2oi4ji-FHuOrXEsxLoYsnckFoX2WYHZwqh5ZGuq7snA@mail.gmail.com>
2015-05-12 15:04 ` Re: Sam Leffler
2015-01-28 7:15 "brcmfmac: brcmf_sdio_htclk: HT Avail timeout" on Thinkpad Tablet 10 Sébastien Bourdeauducq
2015-01-30 14:40 ` Arend van Spriel
2015-09-09 16:55 ` Oleg Kostyuchenko
2013-08-28 11:07 Marc Murphy
2013-08-28 11:23 ` Sedat Dilek
2013-07-28 14:21 piuvatsa
2013-07-28 9:49 ` Tomas Pospisek
2013-07-08 21:52 Jeffrey (Sheng-Hui) Chu
2013-07-08 22:04 ` Joe Perches
2013-07-09 13:22 ` Re: Arend van Spriel
2013-07-10 9:12 ` Re: Samuel Ortiz
2013-04-12 7:08 Callum Hutchinson
2013-04-15 10:30 ` Rafał Miłecki
[not found] <[PATCH 00/14] mac80211: HT/VHT handling>
2013-02-11 12:38 ` Johannes Berg
2013-02-14 17:40 ` Johannes Berg
2012-02-22 6:50 Vlatka Petričec
2012-02-22 15:28 ` Larry Finger
2012-01-30 19:43 Laurent Bonnans
2012-01-31 5:58 ` Mohammed Shafi
2012-02-01 11:14 ` Re: Mohammed Shafi
2012-02-01 16:27 ` Re: John W. Linville
2012-02-01 17:04 ` Re: Felix Fietkau
2012-02-02 5:37 ` Re: Mohammed Shafi
2012-02-02 12:28 ` Re: Felix Fietkau
2012-02-03 10:12 ` Re: Mohammed Shafi
2012-02-03 14:44 ` Re: Laurent Bonnans
2011-05-01 2:30 Naveen Singh
2011-05-01 9:29 ` Johannes Berg
[not found] <1273519372-21934-1-git-send-email-lrodriguez@atheros.com>
2010-05-10 19:26 ` Re: Luis R. Rodriguez
2010-03-17 13:13 Vasil Lalov
2010-03-19 6:05 ` reinette chatre
2010-03-19 16:49 ` Re: Vasil Lalov
2010-03-19 17:10 ` Re: reinette chatre
2010-03-19 17:42 ` Re: Vasil Lalov
2010-03-13 16:33 Thijs van der Kraan
2010-03-13 18:44 ` Gábor Stefanik
2009-11-18 1:50 Janakiram Sistla
2009-11-18 2:25 ` Janakiram Sistla
2009-11-18 10:53 ` Re: Johannes Berg
2009-11-18 11:31 ` Re: Janakiram Sistla
2009-11-18 13:44 ` Re: John W. Linville
2009-11-18 14:19 ` Re: Janakiram Sistla
2009-11-18 14:45 ` Re: John W. Linville
[not found] <E1M5voF-0003wt-00.counter-strike-bk-ru@f144.mail.ru>
2009-05-18 23:14 ` Re: Andrey Yurovsky
2009-05-19 17:14 ` Re: Gábor Stefanik
2009-05-19 18:32 ` Re: Larry Finger
[not found] <81c556230905061857o52b1ad36v9668c3b7e0da6b76@mail.gmail.com>
2009-05-07 13:03 ` Re: Gábor Stefanik
2009-04-22 18:12 donpetrus
2009-04-22 18:28 ` Michael Buesch
2009-03-18 20:03 David Thornton
2009-03-18 20:04 ` Johannes Berg
2008-09-13 16:10 Edgar Velasco
2008-09-13 19:18 ` Luis R. Rodriguez
[not found] <5f68ea7b0808030333o620917ddt4508cdf207a8c9fe@mail.gmail.com>
2008-08-03 12:52 ` Re: Stefanik Gábor
2008-07-14 16:18 Bruno Randolf
2008-07-14 16:30 ` Bruno Randolf
2008-03-23 16:43 Adam Turk
2008-03-24 7:35 ` Pavel Roskin
[not found] <20071223033633.710907923@polimi.it>
2007-12-23 3:39 ` [PATCH 1/7] rc80211-pid: export human-readable target_pf value to debugfs Stefano Brivio
[not found] ` <20071223120124.39050@gmx.net>
[not found] ` <20071223131135.391cc0bb@morte>
2007-12-23 12:19 ` Mattias Nissler
2007-12-23 12:41 ` Stefano Brivio
2007-03-14 15:32 Larry Finger
2007-03-14 15:37 ` Michael Buesch
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=af31a567-ad40-4bbd-85db-4b6242680423@gmail.com \
--to=rtl8821cerfe2@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=nurofen55@meta.ua \
--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