ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bandhan Pramanik <bandhanpramanik06.foss@gmail.com>
To: ath10k@lists.infradead.org, linux-wireless@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [ath10k][QCA9377] Firmware crashes on Dell Inspiron 5567 (IRQ #16, all modern distro kernels)
Date: Mon, 23 Jun 2025 20:22:57 +0530	[thread overview]
Message-ID: <CD81F065-CDDD-41F6-AECD-167B509F57C6@gmail.com> (raw)
In-Reply-To: <CAEmM+Qh=8tm55Ypa2w3ZtOFFrGXTpKqxue59mVAo_5TVy0RJ6g@mail.gmail.com>

Hello,

An update on the situation.

I installed Fedora KDE Plasma Spin, and the skip_otp option didn't work there. KDE specifically said that the Wi-Fi is still connected but it is not connecting to the Internet (confirming my suspicions as true, that the network interface is not disappearing this time and the Destination Host is unreachable, because of the network card).

Only the following convoluted (and strictly step-by-step) solution seems to potentially work (not tested on my own laptop yet): https://www.reddit.com/r/linux/s/8VKDJ6QeP
(This solution has been taken from the GitHub Issue of the Pop!_OS repo)

I used these exact sequence of steps before, and it worked properly. But this time, I simply wrote the skip_otp option to /etc/modprobe.d, and it didn't work.

Reiterating my point: this issue seriously requires urgent attention because it affects all the stable and longterm kernels as of now.

Thanks,

Bandhan Pramanik


On 23 June 2025 3:01:08 am IST, Bandhan Pramanik <bandhanpramanik06.foss@gmail.com> wrote:
> Hello,
> 
> This is to inform all that constant firmware crashes have been seen in
> the "Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter",
> which was shipped with the Dell Inspiron 5567 laptops. This affects
> every kernel release, including the stable and the longterm ones.
> 
> All the logs have been taken after livebooting an Arch Linux ISO.
> 
> Every distro has been tried, and it has been confirmed that some error
> of this kind is shown in every distro.
> 
> ## Steps to reproduce the issue
> 
> 1. Boot/liveboot any Linux ISO through this card (and possibly, this laptop).
> 2. Wi-Fi network interface appears.
> 3. Connect the Wi-Fi router to the computer.
> 4. A few moments/minutes after that, the touchpad stops working, and
> the network interface cannot even access the Internet anymore (BUT,
> the network interface might disappear, might not disappear).
> 
> ## Affected distros and the necessary workarounds
> 
> This has been the pattern on every distro and their corresponding
> kernels (LMDE, Linux Mint, Pop!_OS, Zorin, Kubuntu, KDE Neon,
> elementaryOS, Fedora, and even Arch). The fix which made these distros
> usable is to add two things:
> 
> - Adding "options ath10k_core skip_otp=y" to a new conf file in /etc/modprobe.d.
> - Adding "pci=noaer" in GRUB kernel parameters so that the logs are
> not flooded with Multiple Correctable Errors.
> 
> To defend my case (that it occurs in the other models of Inspiron 5567
> too), I have recently contacted someone running Linux Mint on the same
> model. The answer was the same: the touchpad and the Wi-Fi stop
> simultaneously.
> 
> ## Some of the limitations
> 
> The kernel was tainted, but the other things have been properly noted
> in case they might provide some useful details. As stated,
> investigating why IRQ #16 is disabled will probably give us the
> answer.
> 
> ## Logs provided
> 
> All the logs in a combined manner can be found here:
> https://gist.github.com/BandhanPramanik/ddb0cb23eca03ca2ea43a1d832a16180
> 
> - Full dmesg: https://gist.github.com/BandhanPramanik/ddb0cb23eca03ca2ea43a1d832a16180#file-dmesg-log
> - Hostnamectl: https://gist.github.com/BandhanPramanik/ddb0cb23eca03ca2ea43a1d832a16180#file-hostnamectl-log
> - lspci: https://gist.github.com/BandhanPramanik/ddb0cb23eca03ca2ea43a1d832a16180#file-lspci-log
> - Modinfo of the driver:
> https://gist.github.com/BandhanPramanik/ddb0cb23eca03ca2ea43a1d832a16180#file-modinfo-log
> - Ping command:
> https://gist.github.com/BandhanPramanik/ddb0cb23eca03ca2ea43a1d832a16180#file-ping-log
> - /proc/interrupts:
> https://gist.github.com/BandhanPramanik/ddb0cb23eca03ca2ea43a1d832a16180#file-proc_interrupts-log
> - IP addr command (Heavily Redacted):
> https://gist.github.com/BandhanPramanik/ddb0cb23eca03ca2ea43a1d832a16180#file-ip_addr-log
> 
> Lastly, this issue on the GitHub repository of Pop!_OS 'might' be
> relevant: https://github.com/pop-os/pop/issues/1470
> 
> It would be highly appreciated if the matter were looked into.
> 
> Thanks,
> 
> Bandhan Pramanik


  reply	other threads:[~2025-06-23 18:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-22 21:31 [ath10k][QCA9377] Firmware crashes on Dell Inspiron 5567 (IRQ #16, all modern distro kernels) Bandhan Pramanik
2025-06-23 14:52 ` Bandhan Pramanik [this message]
2025-06-23 19:39   ` Bandhan Pramanik
2025-06-23 22:36     ` Bandhan Pramanik
2025-07-17 23:14       ` 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=CD81F065-CDDD-41F6-AECD-167B509F57C6@gmail.com \
    --to=bandhanpramanik06.foss@gmail.com \
    --cc=ath10k@lists.infradead.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