Chrome OS Version: v59.0.3071.134 (Official Build)(32-bit)
Chrome OS Platform: AOPEN Chromebox Mini

Note:  The AOPEN Chromebox Mini is based off the Chromebit architecture and does not have an RTC Chip

Overview: When restarting a Chromebox mini without internet the box will jump back in time to when it last acquired the network time.

Steps To Reproduce:
(1)Start the device connected to the internet
(2)Run the device for longer than 5 min
(3)Unplug the internet
(4)Restart the device
(5)The clock on the device will now be set to when the device first acquired the internet time after restart

Expected Result:
First Option: Device remembers trusted time during operation  EG.  Start the device in March device runs until July with internet then a restart occurs.  On restart without internet the device would show july

Second Option: Device keeps an internal time stamp from last known acquisition.  Eg.  Start the device in March and run it to July with no internet.  On restart without internet the device shows July.

Actual Result:
In the first case the device will always show the time at which it was acquired during initial network connection.  The device will show March.

The second case will be the same since the device will always revert to the original time acquisition.  The device will show March.  

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?) Always

What is the impact to the user, and is there a workaround? If so, what is
it?  The issue is for content management providers scheduling with a restart without internet.  A typical operation in do perform a daily restart.  If there is an interruption mid day and a restart occurs without internet than the box will think it is when the daily restart occurs.  Eg.  Daily restart occurs at 3AM, box resets at noon, on restart the box would think it is 3AM and the device would show content for 3AM.  Even if the time was then correctly acquired the content management system would have to notice then update the content to the new schedule.  

Please provide any additional information below. Attach a screen shot or
log if possible.

For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.