From: Support TRINITY <support@trinity-net.com>
To: "Rafael J. Wysocki (Intel)" <rafael@kernel.org>
Cc: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
"Rafael J. Wysocki (Intel)" <rafael@kernel.org>,
regressions <regressions@lists.linux.dev>,
linux-acpi <linux-acpi@vger.kernel.org>,
linux-pm <linux-pm@vger.kernel.org>,
xen-devel <xen-devel@lists.xenproject.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Stable <stable@vger.kernel.org>
Subject: Re: [REGRESSION] ACPI processor/cpuidle change in 6.18.52 breaks bare-metal Xen dom0 boot
Date: Mon, 21 Sep 2026 18:29:32 +0000 (UTC) [thread overview]
Message-ID: <1909296988.289641012.1790015372050.JavaMail.zimbra@trinity-net.com> (raw)
In-Reply-To: <CAJZ5v0geSD8ig9_kcrPZp9FEzF+Oh34HV4F_aqyGF89TYVjDzw@mail.gmail.com>
Hello,
Thank you, that makes sense and matches the behavior I observed.
The Alpine 6.18.52 kernel fails as Xen dom0, while restoring the previous
ACPI idle registration lifecycle makes it boot again. That is consistent
with 13ebeef6a1b9 being present in 6.18.y without the later dependency
that avoids calling acpi_processor_power_init() in the !cpuidle_get_driver()
case.
I will try testing 6.18.52 with commit 0089ce1c056a ("ACPI: processor:
Update cpuidle driver check in __acpi_processor_start()") applied,
instead of using my lifecycle revert.
If that boots successfully on the affected Alpine Xen dom0 hosts, I will
report the result here.
Thanks,
Tony
-----Message original-----
De: Rafael J. Wysocki (Intel) <rafael@kernel.org>
à: Support TRINITY <support@trinity-net.com>
Cc: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>; Rafael J. Wysocki (Intel) <rafael@kernel.org>; regressions <regressions@lists.linux.dev>; linux-acpi <linux-acpi@vger.kernel.org>; linux-pm <linux-pm@vger.kernel.org>; xen-devel <xen-devel@lists.xenproject.org>; linux-kernel <linux-kernel@vger.kernel.org>; Stable <stable@vger.kernel.org>
Envoyé: lundi 21 septembre 2026 20:07 CEST
Sujet : Re: [REGRESSION] ACPI processor/cpuidle change in 6.18.52 breaks bare-metal Xen dom0 boot
On Mon, Sep 21, 2026 at 7:46 PM Support TRINITY <support@trinity-net.com> wrote:
>
> Hello,
>
> Thank you, this matches what I see on the affected Alpine Xen dom0
> systems.
>
> I also tested Linux 6.18.52 with processor=nocst on the Linux kernel
>
> Result: it still fails with the same black screen before dom0 userspace
> and networking come up.
>
> Marek's trace looks consistent with the failure mode I isolated: the
> crash happens from acpi_processor_power_init() while registering the
> cpuidle device.
I think I know what the problem is, see
https://lore.kernel.org/linux-acpi/CAJZ5v0h4giv53a2mPvJYT=fvBTj7vVXs=b7+qC2Q2L35qSTOSA@mail.gmail.com/
next prev parent reply other threads:[~2026-09-21 18:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 15:48 Support TRINITY
2026-09-21 10:00 ` Thorsten Leemhuis
2026-09-21 13:06 ` Support TRINITY
2026-09-21 15:26 ` Rafael J. Wysocki (Intel)
2026-09-21 16:44 ` Marek Marczykowski-Górecki
2026-09-21 17:46 ` Support TRINITY
2026-09-21 18:05 ` Rafael J. Wysocki (Intel)
2026-09-21 18:29 ` Support TRINITY [this message]
2026-09-22 2:23 ` Sasha Levin
2026-09-22 10:04 ` Support TRINITY
2026-09-21 18:03 ` Rafael J. Wysocki (Intel)
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=1909296988.289641012.1790015372050.JavaMail.zimbra@trinity-net.com \
--to=support@trinity-net.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=marmarek@invisiblethingslab.com \
--cc=rafael@kernel.org \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=xen-devel@lists.xenproject.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
all inboxes | Powered by JetHome®