From: Bandhan Pramanik <bandhanpramanik06.foss@gmail.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Manivannan Sadhasivam <mani@kernel.org>,
Jeff Johnson <jjohnson@kernel.org>,
linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org,
ath10k@lists.infradead.org, linux-wireless@vger.kernel.org,
stable@vger.kernel.org
Subject: [PATCH TEST] ath10k: Testing Mani's ASPM patch (QCA9377, v6.16-rc1)
Date: Sun, 17 Aug 2025 15:08:27 +0530 [thread overview]
Message-ID: <db9749a0-9c6a-4781-b5fd-82eb129a9c36@gmail.com> (raw)
In-Reply-To: <04489490-aca2-4e67-8eb2-e95f223ead3c@gmail.com>
Hello everyone,
I was actually trying to build a kernel for someone else using build
automation scripts. They still didn't compile. (Here's the relevant
thread I'm referring to:
https://lore.kernel.org/ath10k/176B76BC-6801-4C3F-A774-9611B43ED4AF@gmail.com/T/#t)
Regardless, I tested the patches by Mani
(https://lore.kernel.org/r/20250716-ath-aspm-fix-v1-0-dd3e62c1b692@oss.qualcomm.com).
Here are the logs:
Without pcie_aspm=off (did not work):
https://gist.github.com/BandhanPramanik/ddb0cb23eca03ca2ea43a1d832a16180/raw/84edf89740919e3cba2ac33e567110b14e2d3627/patch-dmesg
With pcie_aspm=off (worked, no issues observed):
https://gist.github.com/BandhanPramanik/ddb0cb23eca03ca2ea43a1d832a16180/raw/84edf89740919e3cba2ac33e567110b14e2d3627/patch-dmesg-pcie_aspm_off
I'm not fully sure what the logs imply, but thanks, it did work even
after playing YouTube videos for two hours (might not even work in the
future, cannot be certain). Earlier, my laptop had its Wi-Fi turning off
within minutes because of IRQ #16 being flooded, in every kernel I
tested so far. Now, it does work.
There can be seen certain stuff in the second log, where it took some
time to connect to Wi-Fi, but I think it is mostly fine.
Thanks to those who have prepared the patches and those who did bear
with me, but there's one request I still need to make.
For anyone who has built patched kernels for Ubuntu and exported in DEB
files, I would appreciate any guidance or pointers on how to do the
same, as my efforts to use "make deb-pkg" have been futile:
https://github.com/BandhanPramanik/ath10k-patched-kernel-ppa/actions/runs/16975573959/job/48123563881
Bandhan Pramanik
বন্ধন প্রামাণিক
next prev parent reply other threads:[~2025-08-17 9:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 19:17 Instability in ALL stable and LTS distro kernels (IRQ #16 being disabled, PCIe bus errors, ath10k_pci) in Dell Inspiron 5567 Bandhan Pramanik
2025-06-25 20:20 ` Bjorn Helgaas
2025-06-25 22:50 ` Bandhan Pramanik
2025-06-26 17:53 ` Bandhan Pramanik
2025-06-26 23:21 ` Bandhan Pramanik
2025-07-04 19:30 ` Bandhan Pramanik
2025-07-05 13:50 ` Bjorn Helgaas
2025-07-05 15:00 ` Bandhan Pramanik
2025-07-05 19:58 ` Bjorn Helgaas
2025-07-06 23:01 ` Bandhan Pramanik
2025-07-07 6:11 ` Manivannan Sadhasivam
2025-07-09 17:30 ` Bandhan Pramanik
2025-07-10 19:06 ` Bandhan Pramanik
2025-07-11 12:15 ` Bjorn Helgaas
2025-07-11 16:04 ` Bandhan Pramanik
2025-07-11 16:36 ` Bjorn Helgaas
2025-07-12 6:48 ` Bandhan Pramanik
2025-07-29 17:35 ` Bandhan Pramanik
2025-08-17 9:38 ` Bandhan Pramanik [this message]
2025-07-12 19:18 ` Askar Safin
2025-07-13 16:04 ` 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=db9749a0-9c6a-4781-b5fd-82eb129a9c36@gmail.com \
--to=bandhanpramanik06.foss@gmail.com \
--cc=ath10k@lists.infradead.org \
--cc=helgaas@kernel.org \
--cc=jjohnson@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mani@kernel.org \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox