Linux wireless drivers development
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Adrodoc <adrodoc55@googlemail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: Error in rtw89 using Kernel 7.1.4
Date: Fri, 14 Aug 2026 02:21:30 +0000	[thread overview]
Message-ID: <ed3fe21f453744a3ac45484839c1c9f1@realtek.com> (raw)
In-Reply-To: <CAOQMLZU9fzaFNh+vbFR=ZpvkyG=T9UDwaeBVXpRj3fvYZt2D-g@mail.gmail.com>


Adrodoc <adrodoc55@googlemail.com> wrote:
> I have been running kernel 7.1.5-1-cachyos with "sudo iw dev wlan0 set
> power_save off" for the last 3 days (monday to wednesday).
> On monday I had a very bad disconnect, but there was absolutely
> nothing to be seen in dmesg or journalctl, so that was probably some
> router or provider issue.
> Other than that I had no disconnect issues during that time also the
> SER L1 did not occur a single time in those 3 days.
> So now I am pretty sure that the disconnects and SER L1 were due to power_save.
> This makes sense to me given the message "firmware failed to ack for
> leaving ps mode".
> This is the same kernel where I previously had multiple disconnects per day.
> 
> So I guess the next step would be to ignore ASPM and bisect kernels
> for "firmware failed to ack for leaving ps mode", right?

I think so.

> Is there anything I should know about power_save going forward?

Re-enable power save (without doing "sudo iw dev wlan0 set power_save off")
Then, only set driver disable_ps_mode=y and cold reboot. 

I'm not sure if you have tried this, if you have done that, I'd say sorry
in advance. Recently I received too many reports...
Maybe, you can summarize the experiments you have done.



  reply	other threads:[~2026-08-14  2:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-27 14:35 Error in rtw89 using Kernel 7.1.4 Adrodoc
2026-07-28  0:50 ` Ping-Ke Shih
2026-07-28  1:07   ` Ping-Ke Shih
2026-07-28  9:22     ` Adrodoc
2026-07-28 17:55       ` Adrodoc
2026-07-29  0:35         ` Ping-Ke Shih
2026-07-29  8:50           ` Adrodoc
2026-07-29  8:59             ` Adrodoc
2026-08-04 17:12               ` Adrodoc
2026-08-05  1:35                 ` Ping-Ke Shih
2026-08-05  8:43                   ` Adrodoc
2026-08-05 14:30                     ` Adrodoc
2026-08-10  5:36                       ` Ping-Ke Shih
2026-08-10  9:50                         ` Adrodoc
2026-08-11  1:48                           ` Ping-Ke Shih
2026-08-13 19:33                             ` Adrodoc
2026-08-14  2:21                               ` Ping-Ke Shih [this message]
2026-08-10  4:01                     ` 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=ed3fe21f453744a3ac45484839c1c9f1@realtek.com \
    --to=pkshih@realtek.com \
    --cc=adrodoc55@googlemail.com \
    --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