From: Chukun Pan <amadeus@jmu.edu.cn>
To: pkshih@realtek.com
Cc: kvalo@kernel.org, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org, Chukun Pan <amadeus@jmu.edu.cn>
Subject: RE: [PATCH 1/1] wifi: rtw88: 8822b: disable call trace when write RF mode table fail
Date: Fri, 13 Oct 2023 10:38:48 +0800 [thread overview]
Message-ID: <20231013023848.10444-1-amadeus@jmu.edu.cn> (raw)
In-Reply-To: <6991a517301a46159085a0b06d43f319@realtek.com>
Hi, Ping-Ke
> Why do you think this trace is useless? As I see, there is more than one callers.
> Did you meet a real case it throws this trace? If yes, how about the frequency?
[ 217.651858] ------------[ cut here ]------------
[ 217.654813] write RF mode table fail
[ 217.657434] WARNING: CPU: 2 PID: 3705 at 0xffffffffa03df3cb [rtw88_8822b@00000000bf0fde9e+0x35000]
[ 217.662078] Modules linked in: rtw88_8822ce rtw88_8822c rtw88_8822be rtw88_8822b rtw88_8723de ...
[ 217.704412] RIP: 0010:0xffffffffa03df3cb [rtw88_8822b@00000000bf0fde9e+0x35000]
...
[ 217.737232] Call Trace:
[ 217.738683] 0xffffffffa03df943 [rtw88_8822b@00000000bf0fde9e+0x35000]
[ 217.740865] 0xffffffffa0385ab9 [rtw88_core@00000000a8d26f0d+0x1a000]
[ 217.742993] 0xffffffffa0279111 [mac80211@000000003cb4b3bd+0x7b000]
[ 217.745028] 0xffffffffa0239092 [cfg80211@00000000a951c4b5+0x46000]
[ 217.751368] ? 0xffffffffa0238de0 [cfg80211@00000000a951c4b5+0x46000]
[ 217.773278] RIP: 0033:0x7ff0cdf8836c
...
[ 217.789457] ---[ end trace 177712424e9eab4a ]---
As you can see this trace above, I don't think it's useful. This
trace throws up a lot of register values but doesn't point out why.
As long as I plug in the rtl8812bu or rtl8822be wifi modules, this
trace will be thrown every time when the rtw88 driver is loaded.
Thanks,
Chukun
--
2.25.1
next prev parent reply other threads:[~2023-10-13 2:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 14:01 [PATCH 1/1] wifi: rtw88: 8822b: disable call trace when write RF mode table fail Chukun Pan
2023-10-13 1:11 ` Ping-Ke Shih
2023-10-13 2:38 ` Chukun Pan [this message]
2023-10-13 4:23 ` Kalle Valo
2023-10-22 9:09 ` Chukun Pan
2023-10-23 2:22 ` Ping-Ke Shih
2023-10-25 4:01 ` Chukun Pan
2023-10-23 8:21 ` Kalle Valo
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=20231013023848.10444-1-amadeus@jmu.edu.cn \
--to=amadeus@jmu.edu.cn \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.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).