Bug 1455481

Summary:	Command "hwclock -w" failed on HPE Moonshot ProLiant m400
Product:	Red Hat Enterprise Linux 7	Reporter:	Radka Brychtova <rskvaril>
Component:	kernel-aarch64	Assignee:	Karel Zak <kzak>
Status:	CLOSED NOTABUG	QA Contact:	Erico Nunes <ernunes>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.4	CC:	jcm, jshortt, kzak
Target Milestone:	rc
Target Release:	---
Hardware:	aarch64
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-09-01 08:33:44 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1465901, 1472751

Description Radka Brychtova 2017-05-25 09:50:40 UTC

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:

Comment 2 Karel Zak 2017-05-25 09:58:42 UTC

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)

Comment 5 Karel Zak 2017-08-03 11:49:03 UTC

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.

Comment 8 Jon Masters 2017-08-31 20:10:13 UTC

Suggest close as not a bug?