From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@linux.intel.com>,
Atharva Tiwari <atharvatiwarilinuxdev@gmail.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Lukas Wunner <lukas@wunner.de>, Dave Jiang <dave.jiang@intel.com>,
Feng Tang <feng.tang@linux.alibaba.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Andreas Noever <andreas.noever@gmail.com>,
Mika Westerberg <westeri@kernel.org>,
Yehezkel Bernat <YehezkelShB@gmail.com>,
linux-usb@vger.kernel.org
Subject: Re: [PATCH] PCI/portdev: Disable AER for Titan Ridge 4C 2018
Date: Wed, 7 Jan 2026 10:30:21 +0100 [thread overview]
Message-ID: <20260107093021.GN2275908@black.igk.intel.com> (raw)
In-Reply-To: <20260106204801.GA374317@bhelgaas>
On Tue, Jan 06, 2026 at 02:48:01PM -0600, Bjorn Helgaas wrote:
> [+cc Thunderbolt folks]
>
> On Tue, Jan 06, 2026 at 11:00:52AM -0800, Kuppuswamy Sathyanarayanan wrote:
> > On 1/6/2026 10:20 AM, Atharva Tiwari wrote:
> > > Disable AER for Intel Titan Ridge 4C 2018
> > > (used in T2 iMacs, where the warnings appear)
> > > that generates continuous pcieport warnings. such as:
> > >
> > > pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:07:00.0
> > > pcieport 0000:07:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
> > > pcieport 0000:07:00.0: device [8086:15ea] error status/mask=00000080/00002000
> > > pcieport 0000:07:00.0: [ 7] BadDLLP
> > >
> > > (see: https://bugzilla.kernel.org/show_bug.cgi?id=220651)
> > >
> > > macOS also disables AER for Thunderbolt devices and controllers in
> > > their drivers.
> >
> > Why not disable it in BIOS or use noaer command line option?
>
> If the kernel can figure this out by itself, we should do that so
> users don't have to debug issues and figure out how to disable in BIOS
> or use a command line option.
>
> But if this is really a hardware issue, I would expect to see some
> reports on the web, and I can't find AER reports that mention these
> devices except this problem report.
>
> Adding Thunderbolt folks in case they know about any errata.
I wonder if these AER messages are caused by PTM too?
Can you try the latest mainline. It has this commit:
044b9f1a7f4f ("PCI/PTM: Enable only if device advertises relevant role")
and see if that changes anything?
>
> > > Signed-off-by: Atharva Tiwari <atharvatiwarilinuxdev@gmail.com>
> > > ---
> > > drivers/pci/pcie/portdrv.c | 4 +++-
> > > 1 file changed, 3 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/pci/pcie/portdrv.c b/drivers/pci/pcie/portdrv.c
> > > index 38a41ccf79b9..5330a679fcff 100644
> > > --- a/drivers/pci/pcie/portdrv.c
> > > +++ b/drivers/pci/pcie/portdrv.c
> > > @@ -240,7 +240,9 @@ static int get_port_device_capability(struct pci_dev *dev)
> > > if ((pci_pcie_type(dev) == PCI_EXP_TYPE_ROOT_PORT ||
> > > pci_pcie_type(dev) == PCI_EXP_TYPE_RC_EC) &&
> > > dev->aer_cap && pci_aer_available() &&
> > > - (pcie_ports_native || host->native_aer))
> > > + (pcie_ports_native || host->native_aer) &&
> > > + !(dev->vendor == PCI_VENDOR_ID_INTEL &&
> > > + (dev->device >= 0x15EA && dev->device <= 0x15EC)))
> > > services |= PCIE_PORT_SERVICE_AER;
> > > #endif
> > >
> >
> > --
> > Sathyanarayanan Kuppuswamy
> > Linux Kernel Developer
> >
next prev parent reply other threads:[~2026-01-07 9:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e45f4544-7ff4-4e75-b8d0-3ec3480b1444@linux.intel.com>
2026-01-06 20:48 ` [PATCH] PCI/portdev: Disable AER for Titan Ridge 4C 2018 Bjorn Helgaas
2026-01-07 9:30 ` Mika Westerberg [this message]
2026-01-07 9:54 ` Atharva Tiwari
2026-01-07 10:01 ` Lukas Wunner
2026-01-07 10:02 ` Mika Westerberg
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=20260107093021.GN2275908@black.igk.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=atharvatiwarilinuxdev@gmail.com \
--cc=bhelgaas@google.com \
--cc=dave.jiang@intel.com \
--cc=feng.tang@linux.alibaba.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=westeri@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