Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
During running older test from testsuite I found out, that there is problem with command "hwclock -w" - invalid argument. On all other architectures this commands works fine, even in man page is mentioned properly.

Version-Release number of selected component (if applicable):
util-linux-2.23.2-41.el7.aarch64

How reproducible:
allways

Steps to Reproduce:
1. hwclock -w
2.
3.

Actual results:
hwclock: ioctl(RTC_SET_TIME) to /dev/rtc to set the time failed.: Invalid argument

Expected results:
no fail

Additional info:

More information about the machine:

# lscpu
Architecture:          aarch64
Byte Order:            Little Endian
CPU(s):                8
On-line CPU(s) list:   0-7
Thread(s) per core:    1
Core(s) per socket:    8
Socket(s):             1
NUMA node(s):          1
Model:                 1
BogoMIPS:              100.00
NUMA node0 CPU(s):     0-7
Flags:                 fp asimd evtstrm


# cat /sys/class/rtc/rtc0/name
rtc-efi

# hwclock --systohc
ioctl(4, RTC_SET_TIME, {tm_sec=8, tm_min=50, tm_hour=7, tm_mday=25, tm_mon=4, tm_year=117, ...})                                                      = -1 EINVAL (Invalid argument)

Note, I have tried to reproduce this issue on 

   gigabyte-r120-08.khw.lab.eng.bos.redhat.com (rhel7.4)
   apm-mustang-ev3-05.lab.eng.brq.redhat.com (f26)

with 

  hwclock -w
  hwclock -w --rtc /dev/rtc0
  hwclock -w --rtc /dev/rtc

and I have been always unsuccessful (= hwclock works as expected).

Maybe the issue is specific to driver or firmware. 

Unfortunately I have no hostname of the machine where it was originally detected.

Suggest close as not a bug?