rtc02 in ubuntu_ltp_kernel_misc failed with AWS ARM64 a1.metal (TBROK: tst_rtc_gettime() realtime failed: EIO (5))

[Po-Hsu Lin]

Issue spotted on Impish AWS 5.13.0-1008.9 with node a1.metal only (ARM64 bare metal).

Test failed with:
   TBROK: tst_rtc_gettime() realtime failed: EIO (5)

Test log:
<<<test_start>>>
tag=rtc02 stime=1640755339
cmdline="rtc02"
contacts=""
analysis=exit
<<<test_output>>>
tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s
tst_wallclock.c:84: TBROK: tst_rtc_gettime() realtime failed: EIO (5)

Summary:
passed 0
failed 0
broken 1
skipped 0
warnings 0
<<<execution_status>>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=2 corefile=no
cutime=0 cstime=0
<<<test_end>>>

Like rtc01 failure in bug 1955953, this test has passed with 5.13.0-1007.8 with LTP head SHA1 2ac54d426 and 5.13.0-1006.7 + LTP head SHA1 9ce71152b in previous cycles. However, I tried to reproduce this manually and it's failing with 5.13.0-1005 / 1007 and 1008 with the same LTP head (2ac54d426). I am not sure why it has passed in the past.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-1008-aws 5.13.0-1008.9
ProcVersionSignature: User Name 5.13.0-1008.9-aws 5.13.19
Uname: Linux 5.13.0-1008-aws aarch64
ApportVersion: 2.20.11-0ubuntu71
Architecture: arm64
CasperMD5CheckResult: unknown
Date: Wed Dec 29 05:22:33 2021
Ec2AMI: ami-07034c7a75109e2af
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-west-2c
Ec2InstanceType: a1.metal
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
SourcePackage: linux-aws
UpgradeStatus: No upgrade log present (probably fresh install)

[Po-Hsu Lin (cypressyew)]

Test history for 5.13.0-1007.8 with LTP head SHA1 2ac54d426 on a1.metal:
 INFO: Test start time: Wed Nov 17 04:22:06 UTC 2021
 COMMAND: /opt/ltp/bin/ltp-pan -q -e -S -a 51639 -n 51639 -f /tmp/ltp-JCWeLCQEew/alltests -l /dev/null -C /dev/null -T /dev/null
 LOG File: /dev/null
 FAILED COMMAND File: /dev/null
 TCONF COMMAND File: /dev/null
 Running tests.......
 tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s
 rtc02.c:66: TINFO: To set RTC date/time is: 2020-10-09 13:23:30
 rtc02.c:80: TINFO: read RTC date/time is: 2020-10-09 13:23:30
 rtc02.c:86: TPASS: The read RTC time is consistent with set time

 Summary:
 passed 1
 failed 0
 broken 0
 skipped 0
 warnings 0
 INFO: ltp-pan reported all tests PASS
 LTP Version: 20210927
 INFO: Test end time: Wed Nov 17 04:22:06 UTC 2021

Test history for 5.13.0-1006.7 with LTP head SHA1 9ce71152b on a1.metal:
 INFO: Test start time: Thu Nov 4 02:37:57 UTC 2021
 COMMAND: /opt/ltp/bin/ltp-pan -q -e -S -a 46764 -n 46764 -f /tmp/ltp-wwu09znAyM/alltests -l /dev/null -C /dev/null -T /dev/null
 LOG File: /dev/null
 FAILED COMMAND File: /dev/null
 TCONF COMMAND File: /dev/null
 Running tests.......
 tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s
 rtc02.c:66: TINFO: To set RTC date/time is: 2020-10-09 13:23:30
 rtc02.c:80: TINFO: read RTC date/time is: 2020-10-09 13:23:30
 rtc02.c:86: TPASS: The read RTC time is consistent with set time

 Summary:
 passed 1
 failed 0
 broken 0
 skipped 0
 warnings 0
 INFO: ltp-pan reported all tests PASS
 LTP Version: 20210927
 INFO: Test end time: Thu Nov 4 02:37:57 UTC 2021

[Po-Hsu Lin (cypressyew)]

This same issue can be found on the following kernel on the same a1.metal instance as well:
 * H-AWS-5.11.0-1023.24
 * F-AWS-5.4.0-1061.64
 * F-AWS-5.11.0-1023.24~20.04.1
 * F-AWS-5.13.0-1008.9~20.04.2
 * B-AWS-5.4.0-1061.64~18.04.1
 * B-AWS-4.15.0-1118.125

And it did pass in the previous cycle.
The only explanation I can think of is there are some HW related changes in AWS cloud.

[Po-Hsu Lin (cypressyew)]

Didn't see this issue in sru-20220711