From: Ping-Ke Shih <pkshih@realtek.com>
To: "Jeffrey Wälti" <jeffrey@waelti.dev>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: wifi: rtw89: rtw8922ae: HWSI bus lockup during RF recalibration on AP bandwidth change
Date: Thu, 2 Apr 2026 02:36:01 +0000 [thread overview]
Message-ID: <4b0f77fcdaf74da5a1c5e77b83f972df@realtek.com> (raw)
In-Reply-To: <JSFJ7Do8YsCSMLsXH6KLXADJ0-z0Dh-y99PpaSCHiCwp6aikxldPnTr9mXpEAifNezf2gFyPPiHIaobekBeqiM4XVpO8hYKyXvuei4lKVc0=@waelti.dev>
Jeffrey Wälti <jeffrey@waelti.dev> wrote:
>
> Ping-Ke Shih <pkshih@realtek.com> wrote:
>
> > Jeffrey Wälti <jeffrey@waelti.dev> wrote:
> > >
> > > <pkshih@realtek.com> wrote:
> > >
> > > >
> > > > Please try to disable power save and ASPM by
> > > > 1) iw wlan0 set power_save off
>
> I'm sorry, this is my first time interacting with the mailing list and I overlooked the other instructions.
> It seems like disabling power save gets rid of the issue of Wi-Fi timeouts. I haven't been able to
> reproduce the issue with `iw wlan0 set power_save off` yet, even without any of the other fixes on kernel
> 6.19.10 and 7.0-rc6.
>
> > > > 2) reference and install
> > > https://github.com/lwfinger/rtw89/blob/main/70-rtw89.conf
> > > > and then cold reboot.
> >
> > Have you tested with these conditions?
>
> Using this patch eliminates the issue of Bluetooth devices disconnecting, when switching between
> networks.
>
> > [...]
> >
> > > >
> > > > Please help to test the latest kernel 7.0-rc with additional patch [1].
> > > >
> > > > [1]
> > > https://lore.kernel.org/linux-wireless/20260310080146.31113-4-pkshih@realtek
> > > .com/
> >
> > Have you also applied this patch?
>
> I tested kernel 7.0-rc6 with this patch applied on top for ~1 day now and haven't been able to reproduce,
> even with power save enabled. However, it is a bit difficult to reliably trigger the issue as it seems
> to trigger more on certain networks than others etc.
>
> > > >
> > > > Ping-Ke
> > > >
> > > >
> > >
> > > Thank you for coming back to me so quickly, I just encountered the same thing
> > > with kernel 7.0-rc5.
> > >
> >
> > Please confirm my questions above.
> >
> > Ping-Ke
> >
> >
>
> In summary:
> - Disabling power save seems to stop the timeouts but Bluetooth issues remain
> - Disabling ASPM features fixes the Bluetooth issue
> - kernel 7.0-rc6 with the additional patch fixes Wi-Fi timeouts but not the Bluetooth disconnects
>
> I hope that answers your questions.
It looks like additional patch can fix the WiFi timeouts problem, and
disabling ASPM feature can fix Bluetooth issue. I think you can keep
(2) + (3) setting as workaround.
I'd talk with BT coexistence team internally to figure out the cause
of Bluetooth disconnection.
Ping-Ke
next prev parent reply other threads:[~2026-04-02 2:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 10:58 wifi: rtw89: rtw8922ae: HWSI bus lockup during RF recalibration on AP bandwidth change Jeffrey Wälti
2026-03-24 2:02 ` Ping-Ke Shih
2026-03-25 19:25 ` Jeffrey Wälti
2026-03-26 0:23 ` Ping-Ke Shih
2026-04-01 11:24 ` Jeffrey Wälti
2026-04-02 2:36 ` Ping-Ke Shih [this message]
[not found] ` <nPBjkph3lQo2eiuYIDyn7Mx8rg_pYRHNkQ-yyIVecS7isXyz4KC77Kud29sqnGKgCVgZS_IM1Jj28gx1RN4iaLuyKhS_MZVUnXhy-BVGCfQ=@waelti.dev>
2026-04-03 10:43 ` Jeffrey Wälti
2026-04-07 0:38 ` Ping-Ke Shih
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=4b0f77fcdaf74da5a1c5e77b83f972df@realtek.com \
--to=pkshih@realtek.com \
--cc=jeffrey@waelti.dev \
--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