From: Todd Brandt <todd.e.brandt@linux.intel.com>
To: linux-kernel@vger.kernel.org, linux-rtc@vger.kernel.org
Cc: rafael.j.wysocki@intel.com, alexandre.belloni@bootlin.com
Subject: Re: RTC wakealarm file is missing in v6.1-rc1
Date: Mon, 17 Oct 2022 21:32:50 -0700 [thread overview]
Message-ID: <2bad27135167f65565cc02c57baffac821e1cf76.camel@linux.intel.com> (raw)
In-Reply-To: <967cfe4e2dba242352ccd1cd00bdbcfb48bdd697.camel@linux.intel.com>
On Mon, 2022-10-17 at 19:19 -0700, Todd Brandt wrote:
> In the v6.1-rc1 kernel release from about 24 hours ago, the wakealarm
> file for the real time clock appears to be missing. Specifically:
>
> /sys/class/rtc/rtc0/wakealarm
>
> Without this sysfs file, the rtcwake and sleepgraph tools no longer
> function properly (and probably all tools that use the RTC through
> sysfs). I've tested on 10 machines so far and this occurs on all of
> them regardless of the specific hardware.
>
> The issue is in this patch set for the rtc subsystem. If I remove
> this
> commit and rebuild, the issue goes away. I'm in the process of
> bisecting further.
>
> commit b7270c69a36efc61ed6ebd31a8a458f354a6edc0
> Merge: 4ce1b97949cb e5f12a398371
> Author: Linus Torvalds <torvalds@linux-foundation.org>
> Date: Fri Oct 14 18:36:42 2022 -0700
>
> I've opened a bugzilla issue here:
> https://bugzilla.kernel.org/show_bug.cgi?id=216600
>
I've bisected this issue to a single commit. I recommend that this
commit be reverted immediately while Raphael creates a fix. It breaks
linux tools that use the rtc wakealarm.
commit 4919d3eb2ec0ee364f7e3cf2d99646c1b224fae8
Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Date: Wed Oct 12 20:07:01 2022 +0200
rtc: cmos: Fix event handler registration ordering issue
prev parent reply other threads:[~2022-10-18 4:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 2:19 RTC wakealarm file is missing in v6.1-rc1 Todd Brandt
2022-10-18 4:32 ` Todd Brandt [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=2bad27135167f65565cc02c57baffac821e1cf76.camel@linux.intel.com \
--to=todd.e.brandt@linux.intel.com \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
/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).