On 2/18/07, Chuck Mattern <camattern at acm.org> wrote: > -Systems will bog down critically after approximately 24 hours loosing > system time at an increasing rate, We have several IBM boxes (NetVista mostly) @work that would exhibit similar behavior - run normally at first, then after a few hours the system clock practically stops; I measured 2 minutes of wall-clock time for a "sleep 1" to return, and up to 20 seconds for "usleep 1"... Tried updating BIOS, kernel (4.3, 4.4, updates), some combinations of boot time parameters (as in: clock={pit|pmtmr|..}, noapic, acpi=off and the like), without improvement. We just gave up on those due to the lack of time. See also: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=203818 Solution from comment 18 may help (that comment was submitted after we've given up, not sure if it was tried). Cheers, Zoran -- "The most likely way for the world to be destroyed, most experts agree, is by accident. That's where we come in. We're computer professionals. We cause accidents." --Nathaniel Borenstein, inventor of MIME