public inbox for ath12k@lists.infradead.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Gregoire <gregoire.s93@live.fr>, Kalle Valo <kvalo@kernel.org>,
	Baochen Qiang <quic_bqiang@quicinc.com>
Cc: ath12k@lists.infradead.org
Subject: Re: WCN7850 disconnects and reconnects in a loop
Date: Tue, 10 Dec 2024 15:22:57 +0100	[thread overview]
Message-ID: <Z1hOweEsmXrIZByQ@hovoldconsulting.com> (raw)
In-Reply-To: <AS8P190MB12051DDBD84CD88E71C40AD7873F2@AS8P190MB1205.EURP190.PROD.OUTLOOK.COM>

On Mon, Apr 01, 2024 at 11:56:39AM +0200, Gregoire wrote:

> I have a QCNCM865 card with a WCN7850 chipset. I'm running Arch Linux 
> version 6.9.0-rc2-1-mainline.
> 
> I'm experiencing difficulty connecting to any Wi-Fi network; the device 
> connects and reconnects almost immediately.
> 
> Here's a gist containing some logs from dmesg and journalctl related to iwd.
> 
> https://gist.github.com/GreyXor/5e6dc8e610a00c8aab37a1251d36dbc1

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.

Johan


  parent reply	other threads:[~2024-12-10 14:40 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 [this message]
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

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=Z1hOweEsmXrIZByQ@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