From: Bitterblue Smith <rtl8821cerfe2@gmail.com>
To: Yun Lu <luyun_611@163.com>, Jes.Sorensen@gmail.com
Cc: kvalo@kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] wifi: rtl8xxxu: fix authentication timeout due to incorrect RCR value
Date: Thu, 27 Apr 2023 20:01:06 +0300 [thread overview]
Message-ID: <3854af21-822d-75f4-0e74-e1998143d59f@gmail.com> (raw)
In-Reply-To: <20230427020512.1221062-1-luyun_611@163.com>
On 27/04/2023 05:05, Yun Lu wrote:
> From: Yun Lu <luyun@kylinos.cn>
>
> When using rtl8192cu with rtl8xxxu driver to connect wifi, there is a
> probability of failure, which shows "authentication with ... timed out".
> Through debugging, it was found that the RCR register has been inexplicably
> modified to an incorrect value, resulting in the nic not being able to
> receive authenticated frames.
>
> To fix this problem, add regrcr in rtl8xxxu_priv struct, and store
> the RCR value every time the register is writen, and use it the next
> time the register need to be modified.
>
Can this bug be reproduced easily? Is it always the same bits which
are mysteriously cleared from REG_RCR?
next prev parent reply other threads:[~2023-04-27 17:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 2:05 [PATCH] wifi: rtl8xxxu: fix authentication timeout due to incorrect RCR value Yun Lu
2023-04-27 17:01 ` Bitterblue Smith [this message]
2023-04-28 4:30 ` Yun Lu
2023-04-27 18:01 ` Larry Finger
2023-04-28 2:00 ` Larry Finger
2023-04-28 4:25 ` wo
2023-04-28 8:25 ` Kalle Valo
2023-04-28 18:30 ` Larry Finger
2023-04-29 5:16 ` Kalle Valo
[not found] ` <76a784b2.2cb3.187c60f0f68.Coremail.luyun_611@163.com>
2023-04-28 17:06 ` Larry Finger
2023-04-29 3:35 ` Yun Lu
2023-04-30 10:36 ` Bitterblue Smith
2023-05-04 7:39 ` Yun Lu
2023-05-11 2:29 ` Yun Lu
2023-05-11 2:45 ` Larry Finger
2023-05-11 13:56 ` Bitterblue Smith
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=3854af21-822d-75f4-0e74-e1998143d59f@gmail.com \
--to=rtl8821cerfe2@gmail.com \
--cc=Jes.Sorensen@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luyun_611@163.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).