From: Support TRINITY <support@trinity-net.com>
To: Sasha Levin <sashal@kernel.org>
Cc: "Rafael J. Wysocki (Intel)" <rafael@kernel.org>,
"Sasha Levin" <sashal@kernel.org>,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
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: Tue, 22 Sep 2026 10:04:39 +0000 (UTC) [thread overview]
Message-ID: <85435495.299101679.1790071479170.JavaMail.zimbra@trinity-net.com> (raw)
In-Reply-To: <2026-09-21-daily-reply-0001-re-acpi-cpuidle-xen-dom0-6-18@kernel.org>
I have now tested Linux 6.18.52 with commit:
0089ce1c056a ("ACPI: processor: Update cpuidle driver check in __acpi_processor_start()") applied on the affected Alpine Xen dom0 bare-metal host.
Result: it boots successfully.
Xen dom0 comes up correctly, /proc/xen is mounted, xenstored starts, SSH
is reachable, and xl info, xl list, etc... work as expected.
So this confirms that 0089ce1c056a fixes the regression on this affected
Alpine system.
Thank you Rafael for identifying the missing stable dependency.
Regards,
Tony
-----Message original-----
De: Sasha Levin <sashal@kernel.org>
à: Rafael J. Wysocki (Intel) <rafael@kernel.org>
Cc: Sasha Levin <sashal@kernel.org>; Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>; 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>; Support TRINITY <support@trinity-net.com>
Envoyé: mardi 22 septembre 2026 04:23 CEST
Sujet : Re: [REGRESSION] ACPI processor/cpuidle change in 6.18.52 breaks bare-metal Xen dom0 boot
> 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.
Queued for 6.18, thanks.
Please still post the result of that test once you have it.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-09-22 10:42 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
2026-09-22 2:23 ` Sasha Levin
2026-09-22 10:04 ` Support TRINITY [this message]
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=85435495.299101679.1790071479170.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=sashal@kernel.org \
--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®