From: Kalle Valo <kvalo@kernel.org>
To: Baochen Qiang <quic_bqiang@quicinc.com>
Cc: Gregoire Stein <gregoire.s93@live.fr>, <ath12k@lists.infradead.org>
Subject: Re: WCN7850 disconnects and reconnects in a loop
Date: Mon, 08 Apr 2024 11:08:38 +0300 [thread overview]
Message-ID: <87ttkc1dkp.fsf@kernel.org> (raw)
In-Reply-To: <73d44b87-57d1-4737-b6ff-c312a6b64852@quicinc.com> (Baochen Qiang's message of "Mon, 8 Apr 2024 14:09:58 +0800")
Baochen Qiang <quic_bqiang@quicinc.com> writes:
> On 4/4/2024 11:41 PM, Gregoire Stein wrote:
>> Hello,
>> now i'm on the last commit of master-pending
>> (6.9.0-rc2-wt-ath-1-mainline-g853450ce5ca0)
>> here are the various logs you asked for:
>> https://gist.github.com/GreyXor/927e7871e70630beabb522aeddc5891e
>
> Thanks for the logs.
>
> From dmesg and NetworkManager logs, connection and EAPOL frames are
> good, but DHCP transaction fails. IWD logs show 'Del Station' event
> received after EAPOL is done. So guessing 3rd party triggers 'Del
> Station' due to some unkown reasons (DHCP session failed?).
>
> In order to know who triggers 'Del Station', could you help reproduce
> this issue and collect mac80211/cfg80211 trace?
>
> Below steps for your consideration:
>
> 1. enable tracing on mac80211/cfg80211
> # echo 1 > /sys/kernel/debug/tracing/events/cfg80211/enable
> # echo 1 > /sys/kernel/debug/tracing/events/mac80211/enable
This is just a suggestion but it might be helpful to include also driver
and wpasupplicant traces to the same file. For example, here's what we
documented for ath10k:
https://wireless.wiki.kernel.org/en/users/drivers/ath10k/debug#tracing
>> There are iwd, networkmanager and dmesg
>> iwd is launched with -d and the ath12k module with the debug flag
>> thanks
>>
> And one more question, is this issue specific to AP? could you try
> other APs or could you try other client with this same AP? We can do
> comparison to narrow down.
Another things to try narrow down the problem is manually running
wpasupplicant. And also using manual IPs (no DHCP at all) or just use
'iw connect' without encryption.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-04-08 8:08 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 [this message]
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
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=87ttkc1dkp.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath12k@lists.infradead.org \
--cc=gregoire.s93@live.fr \
--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