* rtc-test: invalid alarm value
@ 2021-06-30 11:37 Anatoly Pugachev
2021-07-10 0:07 ` Alexandre Belloni
0 siblings, 1 reply; 2+ messages in thread
From: Anatoly Pugachev @ 2021-06-30 11:37 UTC (permalink / raw)
To: linux-rtc
Hello!
Getting the following on kernel boot:
$ journalctl -b -k --no-hostname --utc
...
Jun 30 11:17:24 kernel: rtc-sun4v rtc-sun4v: registered as rtc0
Jun 30 11:17:24 kernel: rtc-sun4v rtc-sun4v: setting system clock to
2021-06-30T11:17:14 UTC (1625051834)
Jun 30 11:17:24 kernel: rtc-test rtc-test.0: registered as rtc1
Jun 30 11:17:24 kernel: rtc rtc2: invalid alarm value:
18446744073704833233-01-06T00:54:29
Jun 30 11:17:24 kernel: rtc-test rtc-test.1: registered as rtc2
Jun 30 11:17:24 kernel: rtc rtc3: invalid alarm value:
18446744073704833233-01-06T00:54:29
Jun 30 11:17:24 kernel: rtc-test rtc-test.2: registered as rtc3
Does it look correct? And if not, how should it work?
Machine is (LDOM) sparc64 debian sid (BE) with kernel
$ uname -a
Linux ttip 5.13.0 #231 SMP Tue Jun 29 16:05:42 MSK 2021 sparc64 GNU/Linux
Kernel boot logs (dmesg) and kernel config available at
https://github.com/mator/sparc64-dmesg/
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: rtc-test: invalid alarm value
2021-06-30 11:37 rtc-test: invalid alarm value Anatoly Pugachev
@ 2021-07-10 0:07 ` Alexandre Belloni
0 siblings, 0 replies; 2+ messages in thread
From: Alexandre Belloni @ 2021-07-10 0:07 UTC (permalink / raw)
To: Anatoly Pugachev; +Cc: linux-rtc
Hello,
On 30/06/2021 14:37:23+0300, Anatoly Pugachev wrote:
> Hello!
>
> Getting the following on kernel boot:
>
> $ journalctl -b -k --no-hostname --utc
> ...
> Jun 30 11:17:24 kernel: rtc-sun4v rtc-sun4v: registered as rtc0
> Jun 30 11:17:24 kernel: rtc-sun4v rtc-sun4v: setting system clock to
> 2021-06-30T11:17:14 UTC (1625051834)
> Jun 30 11:17:24 kernel: rtc-test rtc-test.0: registered as rtc1
> Jun 30 11:17:24 kernel: rtc rtc2: invalid alarm value:
> 18446744073704833233-01-06T00:54:29
> Jun 30 11:17:24 kernel: rtc-test rtc-test.1: registered as rtc2
> Jun 30 11:17:24 kernel: rtc rtc3: invalid alarm value:
> 18446744073704833233-01-06T00:54:29
> Jun 30 11:17:24 kernel: rtc-test rtc-test.2: registered as rtc3
>
> Does it look correct? And if not, how should it work?
>
rtc-test is not meant to be used in production, it will not work on boot
and the message is expected. I guess the best action would be to simply
disable it.
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2021-07-10 0:07 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-06-30 11:37 rtc-test: invalid alarm value Anatoly Pugachev
2021-07-10 0:07 ` Alexandre Belloni
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.