All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: RE: Problem with 8922ae
Date: Thu, 16 May 2024 01:16:05 +0000	[thread overview]
Message-ID: <a321afd48004484cb1a598fc4f54556c@realtek.com> (raw)
In-Reply-To: <723e1eed-e706-4533-b33b-a880b9a46fd8@lwfinger.net>

Larry Finger <larry.finger@gmail.com> wrote:
> On 5/15/24 7:40 PM, Ping-Ke Shih wrote:
> > Larry Finger <larry.finger@gmail.com> wrote:
> >>
> >> I have been busy with the 8821au driver and had not done anything with the
> >> 8922ae driver in the meantime. Now, I am getting some warhings in the logs:
> >>
> >> This warning came while running a kernel generated from rtw-next with commit
> >> 28818b4d871bc93.
> >>
> >
> > The log said SER occurs. I will check this internally.
> >
> > Question: How frequent you met this warning? and is there a method you can
> > always reproduce this symptom?
> 
> I have had 43 of them in about 7 hours of running time. Unfortunately, I do not
> know how to reproduce them.
> 
> I will try to bisect the problem as they were not present earlier.

Recently we added WoWLAN and BT-coexistence for 8922AE. I think you didn't use
WoWLAN features, so cause might be BT-coexistence. Maybe another try is to turn
off BT if you are using. 

I will setup a PC to see if I can reproduce this problem.

Ping-Ke 


  reply	other threads:[~2024-05-16  1:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-15 19:17 Problem with 8922ae Larry Finger
2024-05-16  0:40 ` Ping-Ke Shih
2024-05-16  0:59   ` Larry Finger
2024-05-16  1:16     ` Ping-Ke Shih [this message]
2024-05-16 15:14       ` Larry Finger
2024-05-17  0:32         ` 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=a321afd48004484cb1a598fc4f54556c@realtek.com \
    --to=pkshih@realtek.com \
    --cc=Larry.Finger@lwfinger.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.