Using time.sleep() in 2 threads causes lockup when hyper-threading is enabled

[Marc 'BlackJack' Rintsch]

In <1146798159.209695.4190 at j33g2000cwa.googlegroups.com>, OlafMeding
wrote:

>> IIRC it was something like an NTP daemon that caused the clock to
>> "jump" a little and (Window's) sleep was confused.
> 
> The problem is not a "jump" but a permanet lockup of the sleep statement.

The "jump" of the system clock might confuse the systems `sleep`
implementation.

Ciao,
	Marc 'BlackJack' Rintsch