Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Bandhan Pramanik <bandhanpramanik06.foss@gmail.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: 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: Re: Instability in ALL stable and LTS distro kernels (IRQ #16 being disabled, PCIe bus errors, ath10k_pci) in Dell Inspiron 5567
Date: Fri, 27 Jun 2025 04:51:19 +0530	[thread overview]
Message-ID: <3214E8BE-0A5D-40E7-A4DC-C1027CD052EC@gmail.com> (raw)
In-Reply-To: <E8A26FD9-13E3-474A-87FF-ED8D27A1F27B@gmail.com>

Just a small update: it's not the fix. Back to square 1. 

On 26 June 2025 11:23:14 pm IST, Bandhan Pramanik <bandhanpramanik06.foss@gmail.com> wrote:
> Hello everyone,
> 
> I think I found it. I used irqpoll and I didn't experience any hiccups with my mouse performance. But the Wi-Fi was still malfunctioning.
> 
> To linux-pci and linux-acpi:
> 
> It's an ath10k problem, sure, but there's something definitely problematic happening if, in the normal state, these Wi-Fi bugs hamper the touchpad movement.
> 
> To ath10k and linux-wireless:
> 
> I tried out "options ath10k_core rawmode = 0" along with "skip_otp=y' and the Wi-Fi seems to work perfectly as of now. It might be the fix, it might not be either. But I think there's something more important to ask: Are there any good resources/documentation on referring to what the different key-value pairs mean? Like, what's the exact documentation through which people arrive at "rawmode=0" or "skip_otp=y"?
> 
> 
> 
> Bandhan
> 
>

  reply	other threads:[~2025-06-26 23:21 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 [this message]
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                                   ` [PATCH TEST] ath10k: Testing Mani's ASPM patch (QCA9377, v6.16-rc1) Bandhan Pramanik
2025-07-12 19:18 ` Instability in ALL stable and LTS distro kernels (IRQ #16 being disabled, PCIe bus errors, ath10k_pci) in Dell Inspiron 5567 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=3214E8BE-0A5D-40E7-A4DC-C1027CD052EC@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=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