rtc-test: invalid alarm value
From: Anatoly Pugachev <hidden>
Date: 2021-06-30 11:37:36
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/