linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Bandhan Pramanik <bandhanpramanik06.foss@gmail.com>,
	Jeff Johnson <jjohnson@kernel.org>
Cc: linux-wireless@vger.kernel.org, linux-pci@vger.kernel.org,
	ath10k@lists.infradead.org,
	Manivannan Sadhasivam <mani@kernel.org>
Subject: Re: Packet loss with QCA9377 (ath10k) on ASUS VivoBook E410KA
Date: Wed, 6 Aug 2025 15:40:18 -0500	[thread overview]
Message-ID: <20250806204018.GA14933@bhelgaas> (raw)
In-Reply-To: <2b41300c-2034-4cad-8549-2622c224330f@gmail.com>

[+cc Jeff, ath10k maintainer, Mani]

On Fri, Aug 01, 2025 at 12:09:01AM +0530, Bandhan Pramanik wrote:
> 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?

ath10k mucks directly with ASPM, which it definitely shouldn't do
because ASPM configuration is extremely sensitive, it involves both
ends of the link, and the PCI core needs to know about it.  So I'm a
little suspicious of some issue there.

Mani recently posted a patch series to clean that up a bit, but it's
not fully cooked yet, and I don't know whether it will help this
situation:
https://lore.kernel.org/r/20250716-ath-aspm-fix-v1-0-dd3e62c1b692@oss.qualcomm.com

Bjorn

  reply	other threads:[~2025-08-06 20:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-31 18:39 Packet loss with QCA9377 (ath10k) on ASUS VivoBook E410KA Bandhan Pramanik
2025-08-06 20:40 ` Bjorn Helgaas [this message]
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=20250806204018.GA14933@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=ath10k@lists.infradead.org \
    --cc=bandhanpramanik06.foss@gmail.com \
    --cc=jjohnson@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mani@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 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).