* RTL8922AE driver issues
@ 2025-05-05 3:50 Samuel Reyes
2025-05-05 8:51 ` Ping-Ke Shih
0 siblings, 1 reply; 9+ messages in thread
From: Samuel Reyes @ 2025-05-05 3:50 UTC (permalink / raw)
To: linux-wireless
Hello,
My WiFi has intermittent connection issues on Arch. My motherboard is
a Gigabyte X870 AORUS ELITE WIFI7.
Even when installing Arch my connection was unstable, dmesg -T is
littered with entries like this:
rtw89_8922ae 0000:07:00.0: failed to update 162 RXBD info: -11
rtw89_8922ae 0000:07:00.0: failed to update 163 RXBD info: -11
rtw89_8922ae 0000:07:00.0: failed to update 32 RXBD info: -11
rtw89_8922ae 0000:07:00.0: failed to release TX skbs
I have not found any information online for this.
I've added this as a file to my /etc/modprobe.d/ folder but it hasn't helped:
options rtw89_pci disable_aspm_l1=y disable_aspm_l1ss=y
options rtw89_core disable_ps_mode=y
Here's my lspci -nnk entry:
Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8922AE
802.11be PCIe Wireless Network Adapter [10ec:8922] (rev 01)
Subsystem: Realtek Semiconductor Co., Ltd. RTL8922AE 802.11be
PCIe Wireless Network Adapter [10ec:8922]
Kernel driver in use: rtw89_8922ae
Kernel modules: rtw89_8922ae
lsmod | grep rtw:
smod |grep rtw
rtw89_8922ae 12288 0
rtw89_8922a 73728 1 rtw89_8922ae
rtw89_pci 118784 1 rtw89_8922ae
rtw89_core 1130496 2 rtw89_8922a,rtw89_pci
mac80211 1757184 2 rtw89_core,rtw89_pci
cfg80211 1441792 3 rtw89_core,rtw89_8922a,mac80211
rfkill 40960 8 rtw89_core,bluetooth,cfg80211
My connection can remain active for a long time but will occasionally
disconnect. Toggling Airplane Mode fixes the issue. Prolonged
downloads, such as a large video game, causes the connection to drop
several times. Toggling Airplane Mode lets the game begin download
each time.
I'm happy to provide as much info as necessary.
Thank you!
^ permalink raw reply [flat|nested] 9+ messages in thread
* RE: RTL8922AE driver issues
2025-05-05 3:50 RTL8922AE driver issues Samuel Reyes
@ 2025-05-05 8:51 ` Ping-Ke Shih
2025-05-05 17:12 ` Samuel Reyes
0 siblings, 1 reply; 9+ messages in thread
From: Ping-Ke Shih @ 2025-05-05 8:51 UTC (permalink / raw)
To: Samuel Reyes, linux-wireless@vger.kernel.org
Samuel Reyes <zohrlaffz@gmail.com> wrote:
>
> Hello,
>
> My WiFi has intermittent connection issues on Arch. My motherboard is
> a Gigabyte X870 AORUS ELITE WIFI7.
>
> Even when installing Arch my connection was unstable, dmesg -T is
> littered with entries like this:
> rtw89_8922ae 0000:07:00.0: failed to update 162 RXBD info: -11
> rtw89_8922ae 0000:07:00.0: failed to update 163 RXBD info: -11
> rtw89_8922ae 0000:07:00.0: failed to update 32 RXBD info: -11
> rtw89_8922ae 0000:07:00.0: failed to release TX skbs
Could you help to enlarge retry count? or even larger.
--- a/drivers/net/wireless/realtek/rtw89/pci.c
+++ b/drivers/net/wireless/realtek/rtw89/pci.c
@@ -228,7 +228,7 @@ int rtw89_pci_sync_skb_for_device_and_validate_rx_info(struct rtw89_dev *rtwdev,
struct sk_buff *skb)
{
struct rtw89_pci_rx_info *rx_info = RTW89_PCI_RX_SKB_CB(skb);
- int rx_tag_retry = 100;
+ int rx_tag_retry = 1000;
int ret;
do {
Since this motherboard is AMD platform, please also try to turn off IOMMU
via kernel command line amd_iommu=off to see it can help.
>
> My connection can remain active for a long time but will occasionally
> disconnect. Toggling Airplane Mode fixes the issue. Prolonged
> downloads, such as a large video game, causes the connection to drop
> several times. Toggling Airplane Mode lets the game begin download
> each time.
Not very sure if disconnection is related to above messages. Try to
disable power save to see if it becomes stable by
sudo iw wlan0 set power_save off
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: RTL8922AE driver issues
2025-05-05 8:51 ` Ping-Ke Shih
@ 2025-05-05 17:12 ` Samuel Reyes
2025-05-06 2:11 ` Ping-Ke Shih
0 siblings, 1 reply; 9+ messages in thread
From: Samuel Reyes @ 2025-05-05 17:12 UTC (permalink / raw)
To: Ping-Ke Shih; +Cc: linux-wireless@vger.kernel.org
Big update, I updated my motherboard to the newest BIOS (vF4) and it
has helped dramatically with the amount of errors in dmesg. But the
issue with the connection dropping after some time remains. I added
amd_iommu=off to my kernel parameters and ran sudo iw wlan0 set
power_save off. I did NOT apply the kernel patch you included yet. I
ran dmesg when my connection dropped and saw a bunch of 'failed to
update XX RXBD info: -11' errors again.
I managed to capture the connection drop in a recording so you can see
what it looks like on my end. My connection will remain 'broken'
indefinitely until I toggle airplane mode.
Video: https://youtu.be/BbVlTU8K9Hg
Thanks for your help!
Samuel Reyes
On Mon, May 5, 2025 at 2:51 AM Ping-Ke Shih <pkshih@realtek.com> wrote:
>
> Samuel Reyes <zohrlaffz@gmail.com> wrote:
> >
> > Hello,
> >
> > My WiFi has intermittent connection issues on Arch. My motherboard is
> > a Gigabyte X870 AORUS ELITE WIFI7.
> >
> > Even when installing Arch my connection was unstable, dmesg -T is
> > littered with entries like this:
> > rtw89_8922ae 0000:07:00.0: failed to update 162 RXBD info: -11
> > rtw89_8922ae 0000:07:00.0: failed to update 163 RXBD info: -11
> > rtw89_8922ae 0000:07:00.0: failed to update 32 RXBD info: -11
> > rtw89_8922ae 0000:07:00.0: failed to release TX skbs
>
> Could you help to enlarge retry count? or even larger.
>
> --- a/drivers/net/wireless/realtek/rtw89/pci.c
> +++ b/drivers/net/wireless/realtek/rtw89/pci.c
> @@ -228,7 +228,7 @@ int rtw89_pci_sync_skb_for_device_and_validate_rx_info(struct rtw89_dev *rtwdev,
> struct sk_buff *skb)
> {
> struct rtw89_pci_rx_info *rx_info = RTW89_PCI_RX_SKB_CB(skb);
> - int rx_tag_retry = 100;
> + int rx_tag_retry = 1000;
> int ret;
>
> do {
>
>
> Since this motherboard is AMD platform, please also try to turn off IOMMU
> via kernel command line amd_iommu=off to see it can help.
>
> >
> > My connection can remain active for a long time but will occasionally
> > disconnect. Toggling Airplane Mode fixes the issue. Prolonged
> > downloads, such as a large video game, causes the connection to drop
> > several times. Toggling Airplane Mode lets the game begin download
> > each time.
>
> Not very sure if disconnection is related to above messages. Try to
> disable power save to see if it becomes stable by
>
> sudo iw wlan0 set power_save off
>
>
>
^ permalink raw reply [flat|nested] 9+ messages in thread
* RE: RTL8922AE driver issues
2025-05-05 17:12 ` Samuel Reyes
@ 2025-05-06 2:11 ` Ping-Ke Shih
[not found] ` <CAD+XiyEQPt9HGngt0XBB7Hf=0tDHHcU+3=E20vhPnC3VL1Y+vg@mail.gmail.com>
0 siblings, 1 reply; 9+ messages in thread
From: Ping-Ke Shih @ 2025-05-06 2:11 UTC (permalink / raw)
To: Samuel Reyes; +Cc: linux-wireless@vger.kernel.org
Samuel Reyes <zohrlaffz@gmail.com> wrote:
> Big update, I updated my motherboard to the newest BIOS (vF4) and it
> has helped dramatically with the amount of errors in dmesg. But the
> issue with the connection dropping after some time remains. I added
> amd_iommu=off to my kernel parameters and ran sudo iw wlan0 set
> power_save off. I did NOT apply the kernel patch you included yet. I
> ran dmesg when my connection dropped and saw a bunch of 'failed to
> update XX RXBD info: -11' errors again.
I don't have clear idea now. Please try my patch first.
I will check internally and will need your help to collect more data.
>
> I managed to capture the connection drop in a recording so you can see
> what it looks like on my end. My connection will remain 'broken'
> indefinitely until I toggle airplane mode.
>
> Video: https://youtu.be/BbVlTU8K9Hg
>
Can you open a terminal to show kernel log next time? I would like to
know disconnection happens along 'failed to update XX RXBD info: -11'.
By the way, please not top-posting in wireless mailing.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: RTL8922AE driver issues
[not found] ` <31b6571789b34b95aca2bca73dca2d62@realtek.com>
@ 2025-05-08 20:34 ` Samuel Reyes
2025-05-09 0:38 ` Ping-Ke Shih
0 siblings, 1 reply; 9+ messages in thread
From: Samuel Reyes @ 2025-05-08 20:34 UTC (permalink / raw)
To: Ping-Ke Shih, linux-wireless
On Wed, May 7, 2025 at 7:23 PM Ping-Ke Shih <pkshih@realtek.com> wrote:
>
> Samuel Reyes <zohrlaffz@gmail.com> wrote:
> > On Mon, May 5, 2025 at 8:11 PM Ping-Ke Shih <pkshih@realtek.com> wrote:
> > >
> > > Samuel Reyes <zohrlaffz@gmail.com> wrote:
> > > > Big update, I updated my motherboard to the newest BIOS (vF4) and it
> > > > has helped dramatically with the amount of errors in dmesg. But the
> > > > issue with the connection dropping after some time remains. I added
> > > > amd_iommu=off to my kernel parameters and ran sudo iw wlan0 set
> > > > power_save off. I did NOT apply the kernel patch you included yet. I
> > > > ran dmesg when my connection dropped and saw a bunch of 'failed to
> > > > update XX RXBD info: -11' errors again.
> > >
> > > I don't have clear idea now. Please try my patch first.
> > > I will check internally and will need your help to collect more data.
> > >
> > > >
> > > > I managed to capture the connection drop in a recording so you can see
> > > > what it looks like on my end. My connection will remain 'broken'
> > > > indefinitely until I toggle airplane mode.
> > > >
> > > > Video: https://youtu.be/BbVlTU8K9Hg
> > > >
> > >
> > > Can you open a terminal to show kernel log next time? I would like to
> > > know disconnection happens along 'failed to update XX RXBD info: -11'.
> > >
> > > By the way, please not top-posting in wireless mailing.
> > >
> >
> > Hi!
> >
> > Thanks again for your assistance.
> >
> > I spent all day yesterday and this morning trying to figure out how to
> > apply your patch and wasn't able to do it. I'm by no means an expert
> > and quickly found that patching a kernel is no easy feat.
>
> What are the problems you met? Below is the rough steps to build driver:
> 1. grab kernel source
> git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
> 2. switch to tag you are using
> eg. git checkout v6.14.2
> 3. install toolchain/kernel header by 'apt install'
> sudo apt install build-essential
> (I don't remember how to install kernel header. Please google it yourself.)
> 4. make driver
> e.g. make -C /lib/modules/6.14.2-061402-generic/build M=/$(KERNEL_SOURCE_PATH)/drivers/net/wireless/realtek/rtw89/
> 5. rmmod/insmod
> ```lsmod | grep rtw89``` can see all rtw89 modules
>
>
> > I wanted to
> > record a before and after video (before your patch and after) of the
> > download, but since I couldn't figure out how to patch my kernel I
> > only have a before video. It has the terminal running so you can see
> > the errors pop up in real time. It's pretty long since I recorded it
> > from the very start of the download. The crash happens at around 11:30
> > into the video: https://youtu.be/2nrLOuY6Pwk
>
> I guess the cause is that RXD can't be recognized and then
> "failed to release TX skbs" can't free TX WD properly, so run out of
> TX resource. Therefore, let's try the patch to see if we can resolve
> 'failed to update XX RXBD info: -11' problem first.
>
> >
> > P.S. I hope this is what you meant about top-posting, I also had to
> > research what that meant and how to avoid it :P
>
> Yes, it is. :)
>
The obstacle was unloading the module which was in use to load in the
patched one. I did it though, I had to boot from an Arch live
environment on a USB.
Anyways the patch works!! dmesg is clear of those pesky RXBD messages
and my download completed without failure. This is the first time I've
been able to make a large download like that without the connection
dropping :)
You'll see the download speed dip a few times (e.g. around 4:45
minutes in the video) over the course of the download, but it always
recovers successfully. In the past those dips were a sign of the
connection dropping.
Video: https://youtu.be/A5PUGaIo_pw
^ permalink raw reply [flat|nested] 9+ messages in thread
* RE: RTL8922AE driver issues
2025-05-08 20:34 ` Samuel Reyes
@ 2025-05-09 0:38 ` Ping-Ke Shih
2025-05-09 6:17 ` Samuel Reyes
0 siblings, 1 reply; 9+ messages in thread
From: Ping-Ke Shih @ 2025-05-09 0:38 UTC (permalink / raw)
To: Samuel Reyes, linux-wireless@vger.kernel.org
Samuel Reyes <zohrlaffz@gmail.com> wrote:
> On Wed, May 7, 2025 at 7:23 PM Ping-Ke Shih <pkshih@realtek.com> wrote:
> >
> > Samuel Reyes <zohrlaffz@gmail.com> wrote:
> > > On Mon, May 5, 2025 at 8:11 PM Ping-Ke Shih <pkshih@realtek.com> wrote:
> > > >
> > > > Samuel Reyes <zohrlaffz@gmail.com> wrote:
> > > > > Big update, I updated my motherboard to the newest BIOS (vF4) and it
> > > > > has helped dramatically with the amount of errors in dmesg. But the
> > > > > issue with the connection dropping after some time remains. I added
> > > > > amd_iommu=off to my kernel parameters and ran sudo iw wlan0 set
> > > > > power_save off. I did NOT apply the kernel patch you included yet. I
> > > > > ran dmesg when my connection dropped and saw a bunch of 'failed to
> > > > > update XX RXBD info: -11' errors again.
> > > >
> > > > I don't have clear idea now. Please try my patch first.
> > > > I will check internally and will need your help to collect more data.
> > > >
> > > > >
> > > > > I managed to capture the connection drop in a recording so you can see
> > > > > what it looks like on my end. My connection will remain 'broken'
> > > > > indefinitely until I toggle airplane mode.
> > > > >
> > > > > Video: https://youtu.be/BbVlTU8K9Hg
> > > > >
> > > >
> > > > Can you open a terminal to show kernel log next time? I would like to
> > > > know disconnection happens along 'failed to update XX RXBD info: -11'.
> > > >
> > > > By the way, please not top-posting in wireless mailing.
> > > >
> > >
> > > Hi!
> > >
> > > Thanks again for your assistance.
> > >
> > > I spent all day yesterday and this morning trying to figure out how to
> > > apply your patch and wasn't able to do it. I'm by no means an expert
> > > and quickly found that patching a kernel is no easy feat.
> >
> > What are the problems you met? Below is the rough steps to build driver:
> > 1. grab kernel source
> > git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
> > 2. switch to tag you are using
> > eg. git checkout v6.14.2
> > 3. install toolchain/kernel header by 'apt install'
> > sudo apt install build-essential
> > (I don't remember how to install kernel header. Please google it yourself.)
> > 4. make driver
> > e.g. make -C /lib/modules/6.14.2-061402-generic/build
> M=/$(KERNEL_SOURCE_PATH)/drivers/net/wireless/realtek/rtw89/
> > 5. rmmod/insmod
> > ```lsmod | grep rtw89``` can see all rtw89 modules
> >
> >
> > > I wanted to
> > > record a before and after video (before your patch and after) of the
> > > download, but since I couldn't figure out how to patch my kernel I
> > > only have a before video. It has the terminal running so you can see
> > > the errors pop up in real time. It's pretty long since I recorded it
> > > from the very start of the download. The crash happens at around 11:30
> > > into the video: https://youtu.be/2nrLOuY6Pwk
> >
> > I guess the cause is that RXD can't be recognized and then
> > "failed to release TX skbs" can't free TX WD properly, so run out of
> > TX resource. Therefore, let's try the patch to see if we can resolve
> > 'failed to update XX RXBD info: -11' problem first.
> >
> > >
> > > P.S. I hope this is what you meant about top-posting, I also had to
> > > research what that meant and how to avoid it :P
> >
> > Yes, it is. :)
> >
>
> The obstacle was unloading the module which was in use to load in the
> patched one. I did it though, I had to boot from an Arch live
> environment on a USB.
That will be easier after this success. :)
>
> Anyways the patch works!! dmesg is clear of those pesky RXBD messages
> and my download completed without failure. This is the first time I've
> been able to make a large download like that without the connection
> dropping :)
Good to hear the good news. I will make a patch for it.
>
> You'll see the download speed dip a few times (e.g. around 4:45
> minutes in the video) over the course of the download, but it always
> recovers successfully. In the past those dips were a sign of the
> connection dropping.
>
For me, these dips seems to be acceptable. If you want to dig further,
I should check PHY rate first via debugfs:
cd /sys/kernel/debug/ieee80211/phy0/rtw89
watch cat phy_info
And, capture video as before.
I admit this is only first step to see if the symptom is caused by
PHY rate. If yes, I need air sniffer to know how it happens. If not,
maybe system enters power save mode or others.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: RTL8922AE driver issues
2025-05-09 0:38 ` Ping-Ke Shih
@ 2025-05-09 6:17 ` Samuel Reyes
2025-05-09 7:00 ` Ping-Ke Shih
0 siblings, 1 reply; 9+ messages in thread
From: Samuel Reyes @ 2025-05-09 6:17 UTC (permalink / raw)
To: Ping-Ke Shih; +Cc: linux-wireless@vger.kernel.org
On Thu, May 8, 2025 at 6:38 PM Ping-Ke Shih <pkshih@realtek.com> wrote:
>
> Samuel Reyes <zohrlaffz@gmail.com> wrote:
> > On Wed, May 7, 2025 at 7:23 PM Ping-Ke Shih <pkshih@realtek.com> wrote:
> > >
> > > Samuel Reyes <zohrlaffz@gmail.com> wrote:
> > > > On Mon, May 5, 2025 at 8:11 PM Ping-Ke Shih <pkshih@realtek.com> wrote:
> > > > >
> > > > > Samuel Reyes <zohrlaffz@gmail.com> wrote:
> > > > > > Big update, I updated my motherboard to the newest BIOS (vF4) and it
> > > > > > has helped dramatically with the amount of errors in dmesg. But the
> > > > > > issue with the connection dropping after some time remains. I added
> > > > > > amd_iommu=off to my kernel parameters and ran sudo iw wlan0 set
> > > > > > power_save off. I did NOT apply the kernel patch you included yet. I
> > > > > > ran dmesg when my connection dropped and saw a bunch of 'failed to
> > > > > > update XX RXBD info: -11' errors again.
> > > > >
> > > > > I don't have clear idea now. Please try my patch first.
> > > > > I will check internally and will need your help to collect more data.
> > > > >
> > > > > >
> > > > > > I managed to capture the connection drop in a recording so you can see
> > > > > > what it looks like on my end. My connection will remain 'broken'
> > > > > > indefinitely until I toggle airplane mode.
> > > > > >
> > > > > > Video: https://youtu.be/BbVlTU8K9Hg
> > > > > >
> > > > >
> > > > > Can you open a terminal to show kernel log next time? I would like to
> > > > > know disconnection happens along 'failed to update XX RXBD info: -11'.
> > > > >
> > > > > By the way, please not top-posting in wireless mailing.
> > > > >
> > > >
> > > > Hi!
> > > >
> > > > Thanks again for your assistance.
> > > >
> > > > I spent all day yesterday and this morning trying to figure out how to
> > > > apply your patch and wasn't able to do it. I'm by no means an expert
> > > > and quickly found that patching a kernel is no easy feat.
> > >
> > > What are the problems you met? Below is the rough steps to build driver:
> > > 1. grab kernel source
> > > git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
> > > 2. switch to tag you are using
> > > eg. git checkout v6.14.2
> > > 3. install toolchain/kernel header by 'apt install'
> > > sudo apt install build-essential
> > > (I don't remember how to install kernel header. Please google it yourself.)
> > > 4. make driver
> > > e.g. make -C /lib/modules/6.14.2-061402-generic/build
> > M=/$(KERNEL_SOURCE_PATH)/drivers/net/wireless/realtek/rtw89/
> > > 5. rmmod/insmod
> > > ```lsmod | grep rtw89``` can see all rtw89 modules
> > >
> > >
> > > > I wanted to
> > > > record a before and after video (before your patch and after) of the
> > > > download, but since I couldn't figure out how to patch my kernel I
> > > > only have a before video. It has the terminal running so you can see
> > > > the errors pop up in real time. It's pretty long since I recorded it
> > > > from the very start of the download. The crash happens at around 11:30
> > > > into the video: https://youtu.be/2nrLOuY6Pwk
> > >
> > > I guess the cause is that RXD can't be recognized and then
> > > "failed to release TX skbs" can't free TX WD properly, so run out of
> > > TX resource. Therefore, let's try the patch to see if we can resolve
> > > 'failed to update XX RXBD info: -11' problem first.
> > >
> > > >
> > > > P.S. I hope this is what you meant about top-posting, I also had to
> > > > research what that meant and how to avoid it :P
> > >
> > > Yes, it is. :)
> > >
> >
> > The obstacle was unloading the module which was in use to load in the
> > patched one. I did it though, I had to boot from an Arch live
> > environment on a USB.
>
> That will be easier after this success. :)
>
> >
> > Anyways the patch works!! dmesg is clear of those pesky RXBD messages
> > and my download completed without failure. This is the first time I've
> > been able to make a large download like that without the connection
> > dropping :)
>
> Good to hear the good news. I will make a patch for it.
>
> >
> > You'll see the download speed dip a few times (e.g. around 4:45
> > minutes in the video) over the course of the download, but it always
> > recovers successfully. In the past those dips were a sign of the
> > connection dropping.
> >
>
> For me, these dips seems to be acceptable. If you want to dig further,
> I should check PHY rate first via debugfs:
>
> cd /sys/kernel/debug/ieee80211/phy0/rtw89
> watch cat phy_info
>
> And, capture video as before.
>
> I admit this is only first step to see if the symptom is caused by
> PHY rate. If yes, I need air sniffer to know how it happens. If not,
> maybe system enters power save mode or others.
>
> Good to hear the good news. I will make a patch for it.
Thank you, that's great news!! I'm glad this will prevent this issue
from happening to other people.
> For me, these dips seems to be acceptable. If you want to dig further,
> I should check PHY rate first via debugfs:
>
> cd /sys/kernel/debug/ieee80211/phy0/rtw89
> watch cat phy_info
>
> And, capture video as before.
>
> I admit this is only first step to see if the symptom is caused by
> PHY rate. If yes, I need air sniffer to know how it happens. If not,
> maybe system enters power save mode or others.
I agree, they don't make a meaningful impact on my connection. For the
sake of getting to the bottom of the issue I went ahead and followed
your advice. I recorded 5 of those dips, they can be found at the
following timestamps within the video: 2:45, 5:40, 10:47, 13:12, and
15:50.
Video: https://youtu.be/h7v-qSGEbH0
^ permalink raw reply [flat|nested] 9+ messages in thread
* RE: RTL8922AE driver issues
2025-05-09 6:17 ` Samuel Reyes
@ 2025-05-09 7:00 ` Ping-Ke Shih
2025-05-09 16:49 ` Samuel Reyes
0 siblings, 1 reply; 9+ messages in thread
From: Ping-Ke Shih @ 2025-05-09 7:00 UTC (permalink / raw)
To: Samuel Reyes; +Cc: linux-wireless@vger.kernel.org
Samuel Reyes <zohrlaffz@gmail.com> wrote:
> On Thu, May 8, 2025 at 6:38 PM Ping-Ke Shih <pkshih@realtek.com> wrote:
> >
> > Samuel Reyes <zohrlaffz@gmail.com> wrote:
> > > On Wed, May 7, 2025 at 7:23 PM Ping-Ke Shih <pkshih@realtek.com> wrote:
> > For me, these dips seems to be acceptable. If you want to dig further,
> > I should check PHY rate first via debugfs:
> >
> > cd /sys/kernel/debug/ieee80211/phy0/rtw89
> > watch cat phy_info
> >
> > And, capture video as before.
> >
> > I admit this is only first step to see if the symptom is caused by
> > PHY rate. If yes, I need air sniffer to know how it happens. If not,
> > maybe system enters power save mode or others.
>
> I agree, they don't make a meaningful impact on my connection. For the
> sake of getting to the bottom of the issue I went ahead and followed
> your advice. I recorded 5 of those dips, they can be found at the
> following timestamps within the video: 2:45, 5:40, 10:47, 13:12, and
> 15:50.
At the first dip (2:45), the RX packets drop to zeros. Others' PHY rate
looks normal and only RX counter is smaller. Seemingly it isn't simple to
address problems, so I would like to stop digging. How about you?
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: RTL8922AE driver issues
2025-05-09 7:00 ` Ping-Ke Shih
@ 2025-05-09 16:49 ` Samuel Reyes
0 siblings, 0 replies; 9+ messages in thread
From: Samuel Reyes @ 2025-05-09 16:49 UTC (permalink / raw)
To: Ping-Ke Shih; +Cc: linux-wireless@vger.kernel.org
On Fri, May 9, 2025 at 1:00 AM Ping-Ke Shih <pkshih@realtek.com> wrote:
>
> Samuel Reyes <zohrlaffz@gmail.com> wrote:
> > On Thu, May 8, 2025 at 6:38 PM Ping-Ke Shih <pkshih@realtek.com> wrote:
> > >
> > > Samuel Reyes <zohrlaffz@gmail.com> wrote:
> > > > On Wed, May 7, 2025 at 7:23 PM Ping-Ke Shih <pkshih@realtek.com> wrote:
> > > For me, these dips seems to be acceptable. If you want to dig further,
> > > I should check PHY rate first via debugfs:
> > >
> > > cd /sys/kernel/debug/ieee80211/phy0/rtw89
> > > watch cat phy_info
> > >
> > > And, capture video as before.
> > >
> > > I admit this is only first step to see if the symptom is caused by
> > > PHY rate. If yes, I need air sniffer to know how it happens. If not,
> > > maybe system enters power save mode or others.
> >
> > I agree, they don't make a meaningful impact on my connection. For the
> > sake of getting to the bottom of the issue I went ahead and followed
> > your advice. I recorded 5 of those dips, they can be found at the
> > following timestamps within the video: 2:45, 5:40, 10:47, 13:12, and
> > 15:50.
>
> At the first dip (2:45), the RX packets drop to zeros. Others' PHY rate
> looks normal and only RX counter is smaller. Seemingly it isn't simple to
> address problems, so I would like to stop digging. How about you?
>
>
That works for me. Thanks for all of your help!
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2025-05-09 16:49 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-05-05 3:50 RTL8922AE driver issues Samuel Reyes
2025-05-05 8:51 ` Ping-Ke Shih
2025-05-05 17:12 ` Samuel Reyes
2025-05-06 2:11 ` Ping-Ke Shih
[not found] ` <CAD+XiyEQPt9HGngt0XBB7Hf=0tDHHcU+3=E20vhPnC3VL1Y+vg@mail.gmail.com>
[not found] ` <31b6571789b34b95aca2bca73dca2d62@realtek.com>
2025-05-08 20:34 ` Samuel Reyes
2025-05-09 0:38 ` Ping-Ke Shih
2025-05-09 6:17 ` Samuel Reyes
2025-05-09 7:00 ` Ping-Ke Shih
2025-05-09 16:49 ` Samuel Reyes
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox