From: Bjorn Helgaas <helgaas@kernel.org>
To: Bandhan Pramanik <bandhanpramanik06.foss@gmail.com>
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: Sat, 5 Jul 2025 08:50:20 -0500 [thread overview]
Message-ID: <20250705135020.GA2006390@bhelgaas> (raw)
In-Reply-To: <B0A6D9B4-086F-4D58-8284-485B9FF4B31A@gmail.com>
On Sat, Jul 05, 2025 at 01:00:23AM +0530, Bandhan Pramanik wrote:
> Hi everyone,
>
> Here after a week. I did my research.
>
> I talked to some folks on IRC and the glaring issue was basically this:
>
> > [ 1146.810055] pcieport 0000:00:1c.0: AER: Uncorrectable (Fatal) error message received from 0000:01:00.0
Where is the complete dmesg log from which this is extracted?
> This basically means that the root port (that 1c thing written with
> colons) of PCIe is the main problem here.
>
> One particular note: this issue can be reproduced on the models of
> this same laptop. Therefore, this happens in most if not all of the
> laptops of the same model.
>
> For starters, the root port basically manages the communication
> between the CPU and the device. Now, this root port itself is
> reporting fatal errors.
>
> This is not a Wi-Fi error, but something deeper.
Devices that support AER have extra log registers to capture details
about an error. A device that detects an error sends a PCIe Error
Message upstream to a Root Port. The Root Port generates an
interrupt, which is handled by the aer driver. In this case, the
01:00.0 device detected an error and sent an ERR_FATAL message
upstream, and the 00:1c.0 Root Port received it and generated an
interrupt. The ERR_FATAL message doesn't contain any details about
the error itself, so the aer driver looks for the AER registers in the
01:00.0 device and logs those details to the dmesg log. Normally
there would be a few lines after the one you quoted that would include
those details.
Bjorn
next prev parent reply other threads:[~2025-07-05 13:50 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 [this message]
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=20250705135020.GA2006390@bhelgaas \
--to=helgaas@kernel.org \
--cc=ath10k@lists.infradead.org \
--cc=bandhanpramanik06.foss@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).