From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: "Timur Kristóf" <timur.kristof@gmail.com>
Cc: linux-rtc@vger.kernel.org
Subject: Re: rtc_cmos 00:01: nvmem registration failed
Date: Fri, 25 May 2018 11:39:22 +0200 [thread overview]
Message-ID: <20180525093922.GA2500@piout.net> (raw)
In-Reply-To: <fa7eee0178fe888859730e7ce41e8e8af512f685.camel@gmail.com>
Hi,
On 25/05/2018 11:23:43+0200, Timur Kristóf wrote:
> Hi,
>
> I've used kernel 4.17 rc5 and now using rc6 on Fedora 28 on a Dell XPS
> 13 9370 machine. Since upgrading to this kernel, I get the following
> messages in the journal:
>
> máj 25 08:54:06 timur-xps kernel: rtc_cmos 00:01: RTC can wake from S4
> máj 25 08:54:06 timur-xps kernel: rtc_cmos 00:01: registered as rtc0
> máj 25 08:54:06 timur-xps kernel: rtc_cmos 00:01: nvmem registration failed
> máj 25 08:54:06 timur-xps kernel: rtc_cmos 00:01: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
>
> The "nvmem registration failed" is highlighted red in the journal, and also shows up on every boot.
>
This is probably fixed by
https://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux.git/commit/?h=rtc-next&id=c59b3715ac16544f8f68ab7af03f108e339b36aa
> This where the error message comes from:
> https://github.com/torvalds/linux/blob/master/drivers/rtc/rtc-cmos.c#L818
> And this is the commit that introduced it:
> https://github.com/torvalds/linux/commit/8b5b7958fd1cac54bdca62ec5552c6be0b38def4#diff-4dcdf420d40078042c28f0f3d8d6535c
>
> The error message doesn't give any indication about why it failed.
> How can I help diagnose the what the problem is?
>
My guess is that CONFIG_RTC_NVMEM is not enabled on your kernel.
--
Alexandre Belloni, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-05-25 9:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-25 9:23 rtc_cmos 00:01: nvmem registration failed Timur Kristóf
2018-05-25 9:39 ` Alexandre Belloni [this message]
2018-05-26 21:04 ` Timur Kristóf
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=20180525093922.GA2500@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=linux-rtc@vger.kernel.org \
--cc=timur.kristof@gmail.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).