search for: sys_nanosleep

..._hrtimer_start_range_ns+0x1a3/0x460 [<ffffffff814ee5db>] ? do_nanosleep+0x8b/0xc0 [<ffffffff81095da4>] ? hrtimer_nanosleep+0xc4/0x180 [<ffffffff81094b70>] ? hrtimer_wakeup+0x0/0x30 [<ffffffff81095bd4>] ? hrtimer_start_range_ns+0x14/0x20 [<ffffffff81095ed4>] ? sys_nanosleep+0x74/0x80 [<ffffffff8100b0f2>] ? system_call_fastpath+ thank you Rick

...hich has the following symptoms with paravirtualized guests: - after a live migrate, the time on the guest can jump - after a live migrate, the guest "forgets" to wake up processes - after a domU save, dom0 reboot and domU restore, the time is correct but processes are not woken up from sys_nanosleep The problem seems to stem from the fact that domU uses the hypervisor''s system_time, which is the time since hypervisor system bootup in nanoseconds, as its base for timekeeping. This works fine as long as the guest stays on the same hypervisor, but if the guest is migrated to a hypervis...

Hi, We are trying to validate Asterisk as a media gateway PRI <-> SIP with two T400P (8 T1s) per box. The first experience with BOX1 (Compaq, 2.53 GHz, 1 Gb RAM) and just one T400P was encouraging - on the load test with 3 T1s worth of calls we had on average 75% idle CPU. Not so with BOX2 (Dell, single 2.6 GHz Xeon, 1 Gb RAM, 2 T400P) and BOX3 (Dell, dual 2.6 GHz Xeon, 2 Gb RAM, 2 T400P,