public inbox for ath12k@lists.infradead.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Kalle Valo <kvalo@kernel.org>
Cc: Gregoire <gregoire.s93@live.fr>,
	Baochen Qiang <quic_bqiang@quicinc.com>,
	ath12k@lists.infradead.org
Subject: Re: WCN7850 disconnects and reconnects in a loop
Date: Wed, 25 Jun 2025 11:57:13 +0200	[thread overview]
Message-ID: <aFvH-eKxTOVm3r2U@hovoldconsulting.com> (raw)
In-Reply-To: <87r06dpbst.fsf@kernel.org>

On Thu, Dec 12, 2024 at 10:04:18AM +0200, Kalle Valo wrote:
> Johan Hovold <johan@kernel.org> writes:
> 
> > On Wed, Dec 11, 2024 at 09:35:37AM +0200, Kalle Valo wrote:
> >> Johan Hovold <johan@kernel.org> writes:
> >
> >> > I'm seeing iwd repeatedly failing to connect with reason
> >> > PREV_AUTH_NOT_VALID with WCN7850 on the Lenovo ThinkPad T14s (and the
> >> > Snapdragon X1E CRD reference design).
> >> >
> >> > I first noticed this with 6.10 when starting to work on the Qualcomm X
> >> > Elite platform, but never got around to investigating it. I've confirmed
> >> > that the issue is still there with 6.13-rc1 and that adding
> >> > ControlPortOverNL80211=false allows iwd to connect.
> >> >
> >> > Looking at Gregoire's logs now, it looks like the deauthentication
> >> > reason is different:
> >> >
> >> > 	(Reason: 7=CLASS3_FRAME_FROM_NONASSOC_STA)
> >> >
> >> > instead of
> >> >
> >> > 	(Reason: 2=PREV_AUTH_NOT_VALID)
> >> >
> >> > but the same control port workaround allows iwd to connect.
> >> 
> >> Is there a bugzilla report about this? Unfortunately I have not been
> >> able to follow bugzilla lately due to MLO work but it would be still
> >> good to file this (if that's not done already).
> >
> > Yes, sorry, I should have included the link (it was posted later in the
> > original thread):
> >
> > 	https://bugzilla.kernel.org/show_bug.cgi?id=218733
> 
> No, I should have checked the bugzilla myself but have been too busy.
> Thanks for the link.
> 
> > I only noticed that Gregoire's symptoms were slightly different when
> > replying to this thread. Let me know if you prefer that I file a
> > separate bugzilla report for the PREV_AUTH_NOT_VALID case.
> >
> > The exact same setup (kernel, distro and router) works fine with ath11k
> > and WCN6855 (e.g. as found in the Lenovo ThinkPad X13s).
> 
> Good to know. We need to get this fixed ASAP, I marked it as P1 in bugzilla.

For the record, this appears to have been fix in linux-next now by the
following series:

	https://lore.kernel.org/all/20250523-ath12k-unicast-key-first-v1-0-f53c3880e6d8@quicinc.com/

Johan


      reply	other threads:[~2025-06-25 11:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-01  9:56 WCN7850 disconnects and reconnects in a loop Gregoire
2024-04-03  6:36 ` Baochen Qiang
2024-04-03  6:45   ` Baochen Qiang
2024-04-04 15:41     ` Gregoire Stein
2024-04-08  6:09       ` Baochen Qiang
2024-04-08  8:08         ` Kalle Valo
2024-04-09 10:49           ` Gregoire
2024-04-09 11:39             ` Kalle Valo
2024-04-10  2:23             ` Baochen Qiang
2024-04-11  9:52               ` Gregoire
2024-12-10 14:22 ` Johan Hovold
2024-12-11  7:35   ` Kalle Valo
2024-12-11  9:48     ` Johan Hovold
2024-12-12  8:04       ` Kalle Valo
2025-06-25  9:57         ` Johan Hovold [this message]

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=aFvH-eKxTOVm3r2U@hovoldconsulting.com \
    --to=johan@kernel.org \
    --cc=ath12k@lists.infradead.org \
    --cc=gregoire.s93@live.fr \
    --cc=kvalo@kernel.org \
    --cc=quic_bqiang@quicinc.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