From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Kouroche Bouchiat <kouroche.bouchiat@gmail.com>
Cc: Gilbert Moisio <gmoisio@gmail.com>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: ath10k firmware-6.bin bug: Disconnections every 20 minutes on QCA6174
Date: Thu, 17 Aug 2017 07:14:21 +0000 [thread overview]
Message-ID: <87pobu4qer.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAPYrjBUrEuuxpO=KYi1EXh-bZU2sPNLEsnNZnnp6_w1viss3wQ@mail.gmail.com> (Kouroche Bouchiat's message of "Wed, 16 Aug 2017 16:51:54 +0000")
Kouroche Bouchiat <kouroche.bouchiat@gmail.com> writes:
> Uhm Hello, thank you for the reply Kalle.
> I'm lost. I submitted the original issue about the QCA6174.
>
> I'll try your firmware tonight on my laptop. I've been using
> firmware-4.bin for a week and I haven't had any issues. I'll tell you
> how it performs and attach my dmesg as soon as I can.
I was told that 4.4.1 firmare should have a fix for this. Please let me
know if you can confirm that and then I'll update the firmware in
linux-firmware.
> I was indeed connected to a WPA network. If rekeying happens in
> periodic patterns like that, then it could be where the issue is. I
> can try to see if it occurs on open networks too, if you like.
Yes, WPA rekey is initiated periodically by the AP. Some APs have a
setting in UI to configure the period but not all. But don't bother to
changing WPA rekeying time that as I'm optimistic that 4.4.1 branch has
a fix for your issue.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2017-08-17 7:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-06 22:10 ath10k firmware-6.bin bug: Disconnections every 20 minutes on QCA6174 Kouroche Bouchiat
2017-08-16 14:14 ` Kalle Valo
2017-08-16 14:24 ` Gilbert Moisio
2017-08-16 14:42 ` Kalle Valo
2017-08-16 15:13 ` Gilbert Moisio
2017-08-16 16:26 ` Kalle Valo
[not found] ` <CAM8JFhCpWBDv=_rZ_KDTsQ008wjUgv5nix=kxv-RPd2035xGLQ@mail.gmail.com>
2017-08-17 7:11 ` Kalle Valo
[not found] ` <CAPYrjBUrEuuxpO=KYi1EXh-bZU2sPNLEsnNZnnp6_w1viss3wQ@mail.gmail.com>
2017-08-17 7:14 ` Kalle Valo [this message]
2017-08-17 8:59 ` Kouroche Bouchiat
2017-08-17 13:56 ` Kalle Valo
2017-08-17 15:54 ` Adrian Chadd
2017-08-17 16:03 ` 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=87pobu4qer.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=gmoisio@gmail.com \
--cc=kouroche.bouchiat@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.