From: Ping-Ke Shih <pkshih@realtek.com>
To: Samuel Reyes <zohrlaffz@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: RTL8922AE driver issues
Date: Tue, 6 May 2025 02:11:38 +0000 [thread overview]
Message-ID: <ae5013a930574e68b96544df82f93157@realtek.com> (raw)
In-Reply-To: <CAD+XiyFkogCyQTk8Xhu8htGa892zFkY707+8WVCOdejb3FLNpg@mail.gmail.com>
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.
next prev parent reply other threads:[~2025-05-06 2:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
[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
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=ae5013a930574e68b96544df82f93157@realtek.com \
--to=pkshih@realtek.com \
--cc=linux-wireless@vger.kernel.org \
--cc=zohrlaffz@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox