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
