From: Philippe Schenker <philippe.schenker@impulsing.ch>
To: "rafael@kernel.org" <rafael@kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sasha Levin <sashal@kernel.org>,
"alexandre.belloni@bootlin.com" <alexandre.belloni@bootlin.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-rtc@vger.kernel.org" <linux-rtc@vger.kernel.org>,
"nathan@kernel.org" <nathan@kernel.org>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: [PATCH v2] rtc: cmos: Use platform_get_irq_optional() in cmos_platform_probe()
Date: Thu, 17 Sep 2026 08:26:10 +0000 [thread overview]
Message-ID: <d35e7730006ac5a2ccaa08092201994afea668cb.camel@impulsing.ch> (raw)
In-Reply-To: <12857714.O9o76ZdvQC@rafael.j.wysocki>
[-- Attachment #1: Type: text/plain, Size: 1826 bytes --]
Hi,
this patch did not carry a Cc: stable tag, but the platform device
binding changes it fixes have meanwhile been backported to 6.18.y
(6.18.51), including:
ACPI: x86/rtc-cmos: Use platform device for driver binding
This fix was not backported with it, so 6.18.51 is now affected by
exactly the problem Nathan reported in
https://lore.kernel.org/linux-acpi/20260303060752.GA2749263@ax162/
On my HP ProBook 445 G8 (AMD) the boot log changed as follows:
6.18.49 (good):
rtc_cmos 00:00: alarms up to one month, y3k, 114 bytes nvram
6.18.51 (bad):
rtc_cmos PNP0B00:00: error -ENXIO: IRQ index 0 not found
rtc_cmos PNP0B00:00: no alarms, y3k, 114 bytes nvram
On stable this is more than a confusing message. Without an IRQ the
RTC has no alarm support, so CLOCK_BOOTTIME_ALARM is not available
and systemd (261) refuses suspend-then-hibernate:
systemd-logind: CLOCK_BOOTTIME_ALARM is not supported, can't
perform suspend-then-hibernate.
Call to SuspendThenHibernate failed: Sleep verb
'suspend-then-hibernate' is not configured or configuration is
not supported by kernel
Plain suspend and hibernate still work. RTC wake alarms are also
broken:
# rtcwake -m no -s 120
rtcwake: set rtc wake alarm failed: Invalid argument
The fix is in mainline since v7.0 as:
e9f850ba66cd ("rtc: cmos: Use platform_get_irq_optional() in cmos_platform_probe()")
Stable team, could you please queue it for 6.18.y? Any other stable
series that received the rtc-cmos platform device binding backport
would need it as well.
#regzbot introduced: v6.18.49..v6.18.51
#regzbot title: rtc-cmos: no RTC alarms on x86 in 6.18.y after platform device binding backport
#regzbot fix: rtc: cmos: Use platform_get_irq_optional() in cmos_platform_probe()
Thanks,
Philippe
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 717 bytes --]
next prev parent reply other threads:[~2026-09-17 8:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 12:55 Rafael J. Wysocki
2026-04-03 16:09 ` Alexandre Belloni
2026-09-17 8:26 ` Philippe Schenker [this message]
2026-09-17 8:49 ` Greg Kroah-Hartman
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=d35e7730006ac5a2ccaa08092201994afea668cb.camel@impulsing.ch \
--to=philippe.schenker@impulsing.ch \
--cc=alexandre.belloni@bootlin.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=rafael@kernel.org \
--cc=regressions@lists.linux.dev \
--cc=sashal@kernel.org \
--cc=stable@vger.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
all inboxes | Powered by JetHome®