From: Lukas Wunner <lukas@wunner.de>
To: Aditya Garg <aditya.garg@linux.dev>
Cc: "Perlow, Jason" <jperlow@gmail.com>,
Bjorn Helgaas <helgaas@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
regressions@lists.linux.dev, Alex Deucher <alexdeucher@gmail.com>
Subject: Re: [REGRESSION] PCI/AER: MacBookPro16,1 powers off ~20 s after boot
Date: Tue, 6 Oct 2026 11:44:41 +0200 [thread overview]
Message-ID: <asTDCW28kKBfKAVs@wunner.de> (raw)
In-Reply-To: <2a7a97cc-7ad0-4e6f-845a-dd841d36079b@linux.dev>
On Tue, Oct 06, 2026 at 02:01:52PM +0530, Aditya Garg wrote:
> On 06-10-2026 08:26 am, Lukas Wunner wrote:
> > On Mon, Oct 05, 2026 at 08:17:12PM -0400, Perlow, Jason wrote:
> > > masked only on 04:00.2 (Apple T2 Secure Enclave, 106b:1802):
> > > stays up (120 s)
> > [...]
> > > So here the trigger is unmasking Advisory Non-Fatal Errors on that
> > > one function.
> >
> > That's quite unexpected. Maybe there's a bug in the PCIe IP which
> > Apple used for the T2 Secure Enclave device (which I believe is a
> > fully-fledged arm64 CPU with a PCIe port in Endpoint mode).
[...]
> > macOS likely never unmasks the bit and so they never saw this during
> > validation testing. Is the T2 device visible on Windows? If it is,
> > it seems Windows doesn't support and unmask Advisory Non-Fatal Errors
> > either.
>
> T2 device is visible on Windows as well as "System Device"
It looks like lspci is also available as a Windows binary:
https://github.com/pciutils/pciutils/releases/tag/v3.15.0
https://eternallybored.org/misc/pciutils/
Could you double-check whether it unmasks Advisory Non-Fatal Errors
in the Uncorrectable Error Mask Register, on the T2 or any other device?
Thanks!
Lukas
prev parent reply other threads:[~2026-10-06 9:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 17:53 Perlow, Jason
2026-10-05 18:37 ` Perlow, Jason
2026-10-05 23:19 ` Bjorn Helgaas
2026-10-06 0:17 ` Perlow, Jason
2026-10-06 2:56 ` Lukas Wunner
2026-10-06 8:31 ` Aditya Garg
2026-10-06 9:44 ` Lukas Wunner [this message]
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=asTDCW28kKBfKAVs@wunner.de \
--to=lukas@wunner.de \
--cc=aditya.garg@linux.dev \
--cc=alexdeucher@gmail.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=jperlow@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=regressions@lists.linux.dev \
/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
all inboxes | Powered by JetHome®