Message boards :
Number crunching :
New system time
Message board moderation
| Author | Message |
|---|---|
|
Send message Joined: 15 Dec 11 Posts: 12 Credit: 680,336 RAC: 495  
|
Has anybody seen this before ? Di 20 Feb 2018 17:34:37 CET | | New system time (1519144477) < old system time (1519148074); clearing timeouts It happened yesterday right after booting and today again, causing a lot of accidentally aborted WUs. |
 Send message Joined: 29 Aug 05 Posts: 1108 Credit: 9,319,923 RAC: 0 |
Has anybody seen this before ? Hmm, 1519144477 is equivalent to: 02/20/2018 @ 4:34pm (UTC) and 1519148074 is equivalent to: 02/20/2018 @ 5:34pm (UTC). So you've dropped an hour somewhere (3597 seconds to be precise). Have you been playing with your timezone settings? Or perhaps your CMOS backup battery (usually a 2032 cell) is getting weak and needs replacing?  |
|
Send message Joined: 15 Dec 11 Posts: 12 Credit: 680,336 RAC: 495
|
I did not change any time settings. So, it may be the battery. Even though, the computer is not that old... |
|
Send message Joined: 29 Aug 05 Posts: 1108 Credit: 9,319,923 RAC: 0 |
I did not change any time settings. Tja, the FX-8350 is over 5 years old but It'd depend how soon after that you bought the system. If you have lm_sensors installed and have run sensors-detect you should be able to check Vbat with the sensors command. It shouldn't be much less than 3.3 V in my experience. (Nominal is 3.0 V, mine shows 3.24 V.) |
|
Send message Joined: 15 Dec 11 Posts: 12 Credit: 680,336 RAC: 495
|
lm_sensors says: Vbat: +3.29 V so, maybe a problem with my Linux (Antergos). |
©2025 CERN