I've tried two suspend/resume cycles, one lasting about
10 hours, the last one about 24 hours and the problem didn't occur.
I think this is more of a corner case but am not sure what
the extraordinary set of circumstances is that causes it. Because
the time values were pretty much all increased by the same
amount during/after 'the event' and then continued to increment
normally, I thought perhaps the daylight savings time change
might have been a factor, but the machine wasn't in suspend
state when the switch occurred (March 13 0200 ET here).
I will continue to monitor the stime and the next
time I see a spike will gather all pertinent evidence including
conditions for the previous day. Unless someone can offer any
suggestions for tracing and/or trapping this spike I guess
it's OK to close this.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
