New issue
Advanced search Search tips

Issue 871628 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Aug 7
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

rambi/strago/auron: "hwclock cannot find rtc:"

Project Member Reported by tbroch@chromium.org, Aug 7

Issue description

chromeOS platform: starting with 10930.0.0

What steps will reproduce the problem?
(1) run power_UIResume


What is the expected result?
pass


What happens instead?
08/03 09:47:46.539 WARNI|              test:0637| The test failed with the following exception
Traceback (most recent call last):
  File "/usr/local/autotest/common_lib/test.py", line 598, in _exec
    _cherry_pick_call(self.initialize, *args, **dargs)
  File "/usr/local/autotest/common_lib/test.py", line 746, in _cherry_pick_call
    return func(*p_args, **p_dargs)
  File "/usr/local/autotest/tests/power_Resume/power_Resume.py", line 34, in initialize
    suspend_state=suspend_state)
  File "/usr/local/autotest/cros/power/power_suspend.py", line 134, in __init__
    raise error.TestError('hwclock cannot find rtc: ' + hwclock_output)
TestError: hwclock cannot find rtc: 2018-08-03 09:47:46.900788-07:00

Don't see anything interesting in changelog however,

https://crosland.corp.google.com/log/10929.0.0..10930.0.0


 
Status: Assigned (was: Untriaged)
Summary: rambi/strago/auron: "hwclock cannot find rtc:" (was: rambi: "hwclock cannot find rtc:")
Failure code,

   HWCLOCK_FILE = '/run/power_manager/root/hwclock-on-resume'


        # prime powerd_suspend RTC timestamp saving and make sure hwclock works
        utils.open_write_close(self.HWCLOCK_FILE, '')
        hwclock_output = utils.system_output('hwclock -r --verbose --utc',
                                             ignore_status=True)
        if not re.search('Using.*rtc interface to.*clock', hwclock_output):
            raise error.TestError('hwclock cannot find rtc: ' + hwclock_output)


Seems to work manually however (if tlsdated is stopped)

stop tlsdated ; hwclock -r --verbose --utc ; start tlsdated                                                                                            
tlsdated stop/waiting
hwclock from util-linux 2.32
System Time: 1533654862.218180
Trying to open: /dev/rtc0
Using the rtc interface to the clock.
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2018/08/07 15:14:23
Hw clock time : 2018/08/07 15:14:23 = 1533654863 seconds since 1969
Time since last adjustment is 1533654863 seconds
Calculated Hardware Clock drift is 0.000000 seconds
2018-08-07 08:14:22.764583-07:00
tlsdated start/running, process 19010


Status: WontFix (was: Assigned)
crrev.com/c/1163994 fixed.  Problem was actually that hwclock deprecated --debug arg in favor of --verbose.

Sign in to add a comment