New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 918000 link

Starred by 3 users

Issue metadata

Status: Untriaged
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Feature



Sign in to add a comment

Improve the logic used to determine current system time on boot

Project Member Reported by bigo@chromium.org, Dec 27

Issue description

Description: Improve the logic used to determine current system time on boot.

Use case:
Currently system time on boot is determined by the following:
1) First it looks at RTC if there is battery on the device
2) It looks at the file created by OS when the device is shutdown with the time at shutdown (this is done' only if the shutdown is clean)
3) It looks at timestamp of the Kernel build
4) And default is 0 hours EPOCH time

In crbug.com/903543 on a device with a 32-bit processor, on an unclean shutdown the device seems to ignore this logic and boots with a time back in 2017, although the OS of this device was on 71.

Due to this issue, this caused a bug in the on-screen keyboard in this case to not show.  For kiosk devices, unclean shutdowns are generally the main method that customers use to shutdown devices due to the nature of how these devices are deployed.

The proposed solution is to periodically write the system time to disk, and use that as a reference when booting the device, especially for kiosk devices that are on for extended periods of time.

Motivation:
To improve the time handling on devices, as multiple components rely on accurate time in order to function correctly.


 
Owner: atwilson@chromium.org
Drew, recognize this isn't fully owned by Enterprise team but time sync issues seem to disproportionately impact us as was the case in https://crbug.com/903543.

Why would a device on 71 beta build ever pick a date in 2017? Any reason we can't write timestamp to SSD once an hour or so in order to handle next boot after unclean shutdown better?

Anyhow, would appreciate if you could assign someone to investigate current behavior and determine if we can improve the behavior for enterprise use cases like kiosk.
Labels: -Arch-x86 -RegressedIn-71
Removing labels as this isn't a recent regression afaik and should handle cross-arch time sync behavior

Sign in to add a comment