Bug 1082719

Summary: hwclock error: ioctl(4, RTC_UIE_ON, 0): Invalid argument
Product: [openSUSE] openSUSE Tumbleweed Reporter: Petr Matula <petr.m>
Component: KernelAssignee: E-mail List <kernel-maintainers>
Status: RESOLVED FEATURE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: tiwai
Version: Current   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Petr Matula 2018-02-25 19:51:11 UTC
After longer time I upgraded Raspberry Pi from http://download.opensuse.org/ports/armv6hl/tumbleweed/repo/oss/suse/armv6hl/.

And I tried hwclock --debug with this message "ioctl(4, RTC_UIE_ON, 0): Invalid argument"

hwclock --debug
hwclock from util-linux 2.31.1
System Time: 1519587641.410491
Trying to open: /dev/rtc0
Using the rtc interface to the clock.
Last drift adjustment done at 1519578923 seconds after 1969
Last calibration done at 1519578923 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
ioctl(4, RTC_UIE_ON, 0): Invalid argument
Waiting in loop for time from /dev/rtc0 to change
...got clock tick
Time read from Hardware Clock: 2018/02/25 19:40:43
Hw clock time : 2018/02/25 19:40:43 = 1519587643 seconds since 1969
Time since last adjustment is 8720 seconds
Calculated Hardware Clock drift is 0.000000 seconds
2018-02-25 19:40:42.526296+0000
Comment 1 Takashi Iwai 2018-03-02 07:43:45 UTC
AFAIK, this isn't supported on the platform, so the error is expected.