From: Bert Karwatzki <spasswolf@web.de>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Christian König" <christian.koenig@amd.com>,
"Mario Limonciello (AMD) (kernel.org)" <superm1@kernel.org>,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
regressions@lists.linux.dev, linux-pci@vger.kernel.org,
linux-acpi@vger.kernel.org,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
acpica-devel@lists.linux.dev,
"Robert Moore" <robert.moore@intel.com>,
"Saket Dumbre" <saket.dumbre@intel.com>,
spasswolf@web.de
Subject: Re: Crash during resume of pcie bridge due to infinite loop in ACPICA
Date: Mon, 24 Nov 2025 23:34:37 +0100 [thread overview]
Message-ID: <b1fadb15d1869bde81315be7488c50dbbc9f7dbd.camel@web.de> (raw)
In-Reply-To: <CAJZ5v0iRaYBU+1S4rqYR7D6XC+rfQ2+0hgbodweV5JsFr8EEnQ@mail.gmail.com>
Am Montag, dem 17.11.2025 um 17:40 +0100 schrieb Rafael J. Wysocki:
>
> Well, what you have found appears to be an issue in the AML bytecode
> interpreter which may be one of two things: (1) a bug in the
> interpreter itself or (2) a bytecode issue that causes the interpreter
> to crash (eventually) and the latter is quite a bit more likely.
>
> I'd suggest opening a new issue at
> https://github.com/acpica/acpica/issues and attaching the acpidump
> output from the affected system, to start with.
I've reported the bug to ACPICA github:
https://github.com/acpica/acpica/issues/1060
There's no "infinite" loop, but a loop running for 5051 (0x13BB) iteration until its timeout
counter reaches Zero (most likely because the hardware is unresponsive). Soon (only a
handfull of iterations in the walk loop in acpi_ps_parse_aml()) the crash happens. I think
the crash actually occurs inside acpi_ps_parse_loop(), so I wouldn't rule out an interpreter
bug just yet.
The crash also always happens (if it happens ...) in the 30592th iteration of the walk loop,
so I'm now monitoring the internal of acpi_ps_parse_loop() only in this iteration of the walk
loop. (I've tried to monitor the parse loop before, but that only led to excessive memory
consumption and an activated OOM killer). The debugging code can be found here:
https://gitlab.freedesktop.org/spasswolf/linux-stable/-/commits/amdgpu_suspend_resume?ref_type=heads
So far I've had no crash with this.
Bert Karwatzki
next prev parent reply other threads:[~2025-11-24 22:34 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 12:09 [REGRESSION 00/04] Crash during resume of pcie bridge Bert Karwatzki
2025-10-06 12:09 ` [REGRESSION 01/04] " Bert Karwatzki
2025-10-06 12:09 ` [REGRESSION 02/04] " Bert Karwatzki
2025-10-06 12:09 ` [REGRESSION 03/04] " Bert Karwatzki
2025-10-06 12:09 ` [REGRESSION 04/04] " Bert Karwatzki
2025-10-06 12:39 ` [REGRESSION 00/04] " Christian König
2025-10-06 16:22 ` Bert Karwatzki
2025-10-07 6:50 ` Bert Karwatzki
2025-10-07 21:33 ` Mario Limonciello
2025-10-13 16:29 ` Bert Karwatzki
2025-10-13 18:51 ` Mario Limonciello
2025-10-14 10:50 ` Christian König
[not found] ` <1853e2af7f70cf726df278137b6d2d89d9d9dc82.camel@web.de>
2025-10-31 13:38 ` Bert Karwatzki
2025-10-31 13:47 ` Bert Karwatzki
2025-10-31 18:35 ` Bert Karwatzki
2025-11-05 11:44 ` Bert Karwatzki
2025-11-05 21:31 ` Mario Limonciello (AMD) (kernel.org)
2025-11-07 13:09 ` Bert Karwatzki
2025-11-07 17:09 ` Bert Karwatzki
2025-11-10 13:33 ` Christian König
2025-11-16 21:08 ` Crash during resume of pcie bridge due to infinite loop in ACPICA Bert Karwatzki
2025-11-17 16:40 ` Rafael J. Wysocki
2025-11-24 22:34 ` Bert Karwatzki [this message]
2025-11-25 19:46 ` Rafael J. Wysocki
2025-11-27 0:08 ` Bert Karwatzki
2025-11-27 13:02 ` Rafael J. Wysocki
2025-11-28 20:47 ` Bert Karwatzki
2025-12-02 18:59 ` Rafael J. Wysocki
2025-12-02 19:53 ` Bert Karwatzki
2025-12-02 20:01 ` Rafael J. Wysocki
2025-12-05 10:05 ` Crash during resume of pcie bridge due to incorrect error handling Bert Karwatzki
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=b1fadb15d1869bde81315be7488c50dbbc9f7dbd.camel@web.de \
--to=spasswolf@web.de \
--cc=acpica-devel@lists.linux.dev \
--cc=christian.koenig@amd.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=regressions@lists.linux.dev \
--cc=robert.moore@intel.com \
--cc=saket.dumbre@intel.com \
--cc=superm1@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).