ath10k.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Elia Geretto <elia.f.geretto@gmail.com>
To: ath10k@lists.infradead.org
Subject: Killer WiFi card keeps disconnecting due to latest firmware
Date: Tue, 05 May 2020 10:46:35 +0200	[thread overview]
Message-ID: <0655c3a1466f133a727ab24aec9bb3df81b25d34.camel@gmail.com> (raw)

Hi,

I am experiencing the same problem that Nicola Mori reported on 14th
April. The thread I am referring to is the one with the same subject as
this email.

From what I can understand, Kalle Valo and Wen Gong are trying to
reproduce the problem, but they had difficulties retrieving the correct
hardware. Since I can reproduce the issue with a different router,
probably easier to retrieve, I thought I would dump the information
here.

I have the exact same laptop as Nicola Mori, an XPS 15 9570 and I am
running Fedora 31 (kernel 5.6.8).

The wifi card is reported as:

3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)
	Subsystem: Bigfoot Networks, Inc. Device 1535
	Kernel driver in use: ath10k_pci
	Kernel modules: ath10k_pci

I have tried switching in and out a couple of firmwares with API 6 and
I can reproduce the problem with all the versions I tested:

WLAN.RM.4.4.1-00128-QCARMSWPZ-1
WLAN.RM.4.4.1-00132-QCARMSWP-1
WLAN.RM.4.4.1-00140-QCARMSWPZ-1 (default one on Fedora 31)
WLAN.RM.4.4.1-00151-QCARMSWPZ-2

Regarding the router, it is a Linksys E2500 v3, with firmware 3.0.05
(latest). I use both 2.4 GHz and 5 GHz wireless, with the same SSID.

As for the information regarding the wifi settings:
- Channel: Auto (DFS)
- Channel width: Auto (20 MHz or 40 MHz)
- Encryption: WPA2-Personal

Regarding reproduction, I would like to add that the issue happens
quite rarely. Using my laptop the whole day at max 4 meters from the
router, it happens only once or twice a day.

In addition, when I am unable to start new connections, and
applications like Zoom are still running perfectly, I can work around
the issue not only by disabling and re-enabling the wifi, but also
pinging my laptop from another device in the network. To clarify, when
I am experiencing the issue, if I ping my laptop from my phone, it
starts working correctly again.

I am not sure if this is related, but it happens often, but not
exclusively, when I am using Zoom for videoconferencing. However, I
cannot confirm that it is the cause.

Feel free to contact me for any additional information you may need.

Kind regards,
Elia Geretto


_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

             reply	other threads:[~2020-05-05  8:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-05  8:46 Elia Geretto [this message]
     [not found] <b07a7ea1-7ab2-8ce3-95d7-6726e7708749.ref@aol.com>
2020-04-14  7:26 ` Killer WiFi card keeps disconnecting due to latest firmware Nicola Mori
2020-04-16 12:34   ` Kalle Valo
2020-04-22  7:14     ` Kalle Valo
2020-04-23  9:14       ` Wen Gong
     [not found]         ` <cd1469bf-452c-5819-b5c2-b1ff8c48638f@aol.com>
2020-04-26  9:14           ` Nicola Mori

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=0655c3a1466f133a727ab24aec9bb3df81b25d34.camel@gmail.com \
    --to=elia.f.geretto@gmail.com \
    --cc=ath10k@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).