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: Wed, 5 Aug 2026 01:35:11 +0000	[thread overview]
Message-ID: <013f7d3cf223417c94df41a2a45fa540@realtek.com> (raw)
In-Reply-To: <CAOQMLZUn30NJwU4pR0hL=nz38Mbp=73wgqd+CoQE2qSO3cf4_w@mail.gmail.com>

Adrodoc <adrodoc55@googlemail.com> wrote:
> A little update: I managed to downgrade my linux kernel, but I can't
> install versions older than 6.6.9-arch1-1, because when trying to
> install them I get an error: invalid or corrupted package (PGP
> signature).
> 
> So I ran 6.6.9-arch1-1 for 6 and a half hours today without
> encountering the issue. Yesterday I was running 7.1.5-1-cachyos and
> had the issue 3 times while using my PC for just over 7 hours. So the
> issue is likely not present in 6.6.9-arch1.1.

I suggest you can try 6.6.9-arch1-1 longer. As I checked internal experts
who said the SER symptom can occur on some platforms infrequently because
of hardware flaws. Therefore, if the infrequent SER doesn't bother your
daily work, they suggest to just keep it as was. 

If we want to debug further, my plan is to bisect drivers (or firmware) to
see whether a certain version can work well on your platform, and we can
bisect the commits in detail. At that time, I need your help to build
and test driver ko.

The second way is to debug on the latest kernel and apply debug patch to
dump more detail needed by internal experts. But it seems like this is
still uncertain because of hardware flaw they mentioned.

> 
> I'll try 6.12.10.arch1-1 tomorrow.

Suggest to test 6.6.9-arch1-1 longer as mentioned above.



  reply	other threads:[~2026-08-05  1:35 UTC|newest]

Thread overview: 16+ 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 [this message]
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-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=013f7d3cf223417c94df41a2a45fa540@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