From: Johan Hovold <johan@kernel.org>
To: Johannes Berg <johannes.berg@intel.com>, Kalle Valo <kvalo@kernel.org>
Cc: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: mac80211/ath11k regression in next-20220720
Date: Fri, 22 Jul 2022 09:52:21 +0200 [thread overview]
Message-ID: <YtpXNYta924al1Po@hovoldconsulting.com> (raw)
Hi,
After moving from next-20220714 to next-20220720, ath11k stopped
working here and instead spits out a bunch of warnings (see log below).
I noticed that this series from Johannes was merged in that period:
https://lore.kernel.org/all/20220713094502.163926-1-johannes@sipsolutions.net/
but can't say for sure that it's related. I also tried adding the
follow-up fixes from the mld branch:
https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git/log/?h=mld
but it didn't seem to make any difference.
Any ideas about what might be going on here?
Johan
[ 256.674853] wlan0: authenticate with 70:3a:cb:f7:3a:e4
[ 256.687231] wlan0: bad VHT capabilities, disabling VHT
[ 256.687324] wlan0: Invalid HE elem, Disable HE
[ 256.687389] wlan0: 80 MHz not supported, disabling VHT
[ 256.779398] wlan0: send auth to 70:3a:cb:f7:3a:e4 (try 1/3)
[ 256.788290] wlan0: authenticated
[ 256.807167] wlan0: 80 MHz not supported, disabling VHT
[ 256.823138] wlan0: associate with 70:3a:cb:f7:3a:e4 (try 1/3)
[ 256.932099] wlan0: associate with 70:3a:cb:f7:3a:e4 (try 2/3)
[ 257.047894] wlan0: associate with 70:3a:cb:f7:3a:e4 (try 3/3)
[ 257.156109] wlan0: association with 70:3a:cb:f7:3a:e4 timed out
[ 257.171179] ath11k_pci 0006:01:00.0: failed to lookup peer 70:3a:cb:f7:3a:e4 on vdev 0
[ 257.171340] ------------[ cut here ]------------
[ 257.171360] WARNING: CPU: 4 PID: 71 at drivers/net/wireless/ath/ath11k/mac.c:7181 ath11k_mac_op_unassign_vif_chanctx
+0x1e8/0x2c0 [ath11k]
[ 257.172255] Call trace:
[ 257.172267] ath11k_mac_op_unassign_vif_chanctx+0x1e8/0x2c0 [ath11k]
[ 257.172313] ieee80211_assign_link_chanctx+0x74/0x320 [mac80211]
[ 257.172380] __ieee80211_link_release_channel+0x58/0x150 [mac80211]
[ 257.172443] ieee80211_link_release_channel+0x3c/0x60 [mac80211]
[ 257.172503] ieee80211_destroy_assoc_data+0xcc/0x170 [mac80211]
[ 257.172563] ieee80211_sta_work+0x220/0xa20 [mac80211]
[ 257.172621] ieee80211_iface_work+0x388/0x3f0 [mac80211]
[ 257.172681] process_one_work+0x1cc/0x320
[ 257.172708] worker_thread+0x14c/0x450
[ 257.172729] kthread+0x10c/0x110
[ 257.172747] ret_from_fork+0x10/0x20
[ 257.172768] ---[ end trace 0000000000000000 ]---
[ 257.173752] ------------[ cut here ]------------
[ 257.173771] WARNING: CPU: 4 PID: 71 at drivers/net/wireless/ath/ath11k/mac.c:6813 ath11k_mac_vdev_stop+0x134/0x1a0 [
ath11k]
[ 257.175919] Call trace:
[ 257.177237] ath11k_mac_vdev_stop+0x134/0x1a0 [ath11k]
[ 257.178582] ath11k_mac_op_unassign_vif_chanctx+0x74/0x2c0 [ath11k]
[ 257.179925] ieee80211_assign_link_chanctx+0x74/0x320 [mac80211]
[ 257.181281] __ieee80211_link_release_channel+0x58/0x150 [mac80211]
[ 257.182633] ieee80211_link_release_channel+0x3c/0x60 [mac80211]
[ 257.183990] ieee80211_destroy_assoc_data+0xcc/0x170 [mac80211]
[ 257.185350] ieee80211_sta_work+0x220/0xa20 [mac80211]
[ 257.186779] ieee80211_iface_work+0x388/0x3f0 [mac80211]
[ 257.188137] process_one_work+0x1cc/0x320
[ 257.189455] worker_thread+0x14c/0x450
[ 257.190771] kthread+0x10c/0x110
[ 257.192082] ret_from_fork+0x10/0x20
[ 257.193382] ---[ end trace 0000000000000000 ]---
[ 257.194721] ath11k_pci 0006:01:00.0: failed to find peer vdev_id 0 addr 70:3a:cb:f7:3a:e4 in delete
[ 257.196084] ath11k_pci 0006:01:00.0: failed to delete peer 70:3a:cb:f7:3a:e4 for vdev 0: -22
next reply other threads:[~2022-07-22 7:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 7:52 Johan Hovold [this message]
2022-07-22 7:54 ` mac80211/ath11k regression in next-20220720 Johannes Berg
2022-07-22 8:05 ` Johan Hovold
2022-07-22 8:06 ` Johannes Berg
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=YtpXNYta924al1Po@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=johannes.berg@intel.com \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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