Detected clock skew[...], I/O delay, laptop hibenation or...
Moderators: Site Moderators, FAHC Science Team
Re: Detected clock skew[...], I/O delay, laptop hibenation o
Unlike the GPU FAHCore, the CPU based FAHCore writes checkpoints at designated intervals (default=15 minutes) but the only way to tell when it happens is to look at the date-time stamp on the files. Your description is consistent with that. (no clock skew messages)
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.
Re: Detected clock skew[...], I/O delay, laptop hibenation o
I played around a bit.
It happens on every (re)start.
But i noticed the process as shown by htop is older than the RPi did even start.
And TIME+ is counting fast forward.
If TIME+ is 3h21:xx uptime is 1:12
At uptime 1:37 the TIME+ is 4:34
Now at uptime 1:55 TIME+ shows 5:25
It happens on every (re)start.
But i noticed the process as shown by htop is older than the RPi did even start.
And TIME+ is counting fast forward.
If TIME+ is 3h21:xx uptime is 1:12
At uptime 1:37 the TIME+ is 4:34
Now at uptime 1:55 TIME+ shows 5:25
24/7
1x i5 3470 @2Cores
1x GTX750 (GM107)
2x GTX750Ti (GM107)
1x i5 3470 @2Cores
1x GTX750 (GM107)
2x GTX750Ti (GM107)
Re: Detected clock skew[...], I/O delay, laptop hibenation o
Heres a screenshot of htop and uptime after some more hours.
I checked and none of my other (all x86) machines is doing this.
I checked and none of my other (all x86) machines is doing this.
24/7
1x i5 3470 @2Cores
1x GTX750 (GM107)
2x GTX750Ti (GM107)
1x i5 3470 @2Cores
1x GTX750 (GM107)
2x GTX750Ti (GM107)