From: Bandhan Pramanik <bandhanpramanik06.foss@gmail.com>
To: linux-wireless@vger.kernel.org, linux-pci@vger.kernel.org,
ath10k@lists.infradead.org
Subject: Packet loss with QCA9377 (ath10k) on ASUS VivoBook E410KA
Date: Fri, 1 Aug 2025 00:09:01 +0530 [thread overview]
Message-ID: <2b41300c-2034-4cad-8549-2622c224330f@gmail.com> (raw)
Hello,
I'm helping someone who was having trouble with their Wi-Fi on Asus
VivoBook E410KA. The device uses the QCA9377 Wireless Chip.
The device suffered from a single packet loss within 33 seconds while
running a continuous ping. There might be some PCIe-level communication
problems too.
All the relevant logs can be found here in a redacted form:
First part (ping, hostnamectl, ip addr, lspci):
https://gist.github.com/BandhanPramanik/7eefd192c3a728d2473687a786fbbc01/raw/e77f0fa1cf35c748730df220b0057399ac78f539/miscellaneous
Second part (cat /proc/interrupts, modinfo ath10k_pci):
https://gist.github.com/BandhanPramanik/7eefd192c3a728d2473687a786fbbc01/raw/e77f0fa1cf35c748730df220b0057399ac78f539/miscellaneous%25202
dmesg:
https://gist.github.com/BandhanPramanik/7eefd192c3a728d2473687a786fbbc01/raw/e77f0fa1cf35c748730df220b0057399ac78f539/dmesg
We’re not sure if this is a driver issue, a firmware problem, or maybe
something hardware-specific.
Has anyone seen something similar with this chip? Any tips on how to
troubleshoot or fix the packet loss?
Thanks,
Bandhan Pramanik
বন্ধন প্রামাণিক
next reply other threads:[~2025-07-31 18:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 18:39 Bandhan Pramanik [this message]
2025-08-06 20:40 ` Packet loss with QCA9377 (ath10k) on ASUS VivoBook E410KA Bjorn Helgaas
2025-08-07 6:03 ` Bandhan Pramanik
2025-08-07 8:23 ` Manivannan Sadhasivam
2025-08-07 22:04 ` Bandhan Pramanik
2025-08-27 17:28 ` Bandhan Pramanik
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=2b41300c-2034-4cad-8549-2622c224330f@gmail.com \
--to=bandhanpramanik06.foss@gmail.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-wireless@vger.kernel.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 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.