All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Perlow <jperlow@gmail.com>
To: Lukas Wunner <lukas@wunner.de>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
	Raag Jadav <raag.jadav@intel.com>,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH v2 0/7] Error reporting for AER-incapable devices
Date: Wed, 18 Nov 2026 20:03:35 -0500	[thread overview]
Message-ID: <20261119010335.84545-1-jperlow@gmail.com> (raw)
In-Reply-To: <cover.1794997749.git.lukas@wunner.de>

Tested the full v2 series on v7.4-rc3 (plus out-of-tree T2 patches) on
four x86 machines: two MacBookPro16,1 (Apple T2), an ASUS ROG Zephyrus
M15 GU502LV, and an HP desktop with an Intel 800-series chipset.

Before/after with the same base kernel built with and without the
series: the number of devices that have no AER capability but have all
four Device Control error-enable bits (CorrErr, NonFatalErr, FatalErr,
UnsupReq) set went from 0 of 6 to 5 of 6 (MacBookPro16,1), 0 of 3 to
2 of 3 (ASUS, which needs pcie_ports=native because its firmware
answers "platform does not support [AER]" in _OSC), and 0 of 4 to 2 of
4 (HP). AER-capable devices were already fully enabled. I did not look
into why the remaining devices (for example the integrated GPU on the
ASUS) stay off.

Thunderbolt 4 dock unplug/replug on both MacBooks: no AER or DPC events
and the link came back normally. 10 suspend/resume cycles on each of
the two MacBooks and the ASUS, plus one 25-minute suspend: no AER or
DPC messages and no device loss.

I did not test error injection, so the error-handling paths in patches
3 and 4 were not exercised.

Tested-by: Jason Perlow <jperlow@gmail.com>

  parent reply	other threads:[~2026-11-19  1:03 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-18 10:40 [PATCH v2 0/7] Error reporting for AER-incapable devices Lukas Wunner
2026-11-18 10:40 ` [PATCH v2 1/7] PCI/DPC: Avoid access to non-existent AER capability Lukas Wunner
2026-11-18 11:04   ` sashiko-bot
2026-11-18 16:00   ` Kuppuswamy Sathyanarayanan
2026-11-18 10:40 ` [PATCH v2 2/7] PCI/DPC: Reinstate support for AER-incapable ports Lukas Wunner
2026-11-18 11:03   ` sashiko-bot
2026-11-18 10:40 ` [PATCH v2 3/7] PCI/ERR: Clear error status bits more selectively Lukas Wunner
2026-11-18 11:09   ` sashiko-bot
2026-11-18 16:04   ` Kuppuswamy Sathyanarayanan
2026-11-18 10:40 ` [PATCH v2 4/7] PCI/ERR: Avoid stale error status bits on recovery failure Lukas Wunner
2026-11-18 11:18   ` sashiko-bot
2026-11-18 16:05   ` Kuppuswamy Sathyanarayanan
2026-11-18 10:40 ` [PATCH v2 5/7] PCI/AER: Drop AER native check from handles_cxl_errors() Lukas Wunner
2026-11-18 11:02   ` sashiko-bot
2026-11-18 10:40 ` [PATCH v2 6/7] PCI/AER: Move AER capability check out of pcie_aer_is_native() Lukas Wunner
2026-11-18 11:13   ` sashiko-bot
2026-11-18 10:40 ` [PATCH v2 7/7] PCI/AER: Enable baseline capability error reporting Lukas Wunner
2026-11-18 11:19   ` sashiko-bot
2026-11-18 22:17     ` Lukas Wunner
2026-11-19  1:03 ` Jason Perlow [this message]
2026-11-20 18:19 ` [PATCH v2 0/7] Error reporting for AER-incapable devices Bjorn Helgaas

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=20261119010335.84545-1-jperlow@gmail.com \
    --to=jperlow@gmail.com \
    --cc=helgaas@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=raag.jadav@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.