Problem Description : ThreadInterruptedAndNotified sometimes fails with assertion: "time warp"

Java Release : 1.6.0
Java Builds : b99 and previous builds
VM flavors : client | server
VM Modes : -Xint | -Xcomp | -Xmixed
Java flags :
Platform(s) : linux-i586, linux-amd64
Hostnames with OS info : vmsqe-amd-03 (Linux: RHEL 4.0)

Testbase Name : SQE Testbase
Suite Name : vm.runtime
Test cases : runtime/threads/ThreadInterruptedAndNotified


How to reproduce:
 1. javac -d . ThreadInterruptedAndNotified.java
 2. java runtime.threads.ThreadInterruptedAndNotified.ThreadInterruptedAndNotified

Error log:

/set/vmsqe/jdk-builds/JDK6b99/linux-i586/fastdebug/bin/java -server -Xcomp runtime.threads.ThreadInterruptedAndNotified.ThreadInterruptedAndNotified
Notifier: threads=2, iterations=1000
Notifier: threads=8, iterations=1000
Notifier: threads=32, iterations=1000
Notifier: threads=128, iterations=1000
Java HotSpot(TM) Server VM warning: time warp: -953422407 to 269
Java HotSpot(TM) Server VM warning: time warp: -953422407 to 269
Java HotSpot(TM) Server VM warning: time warp: -953422407 to 269
Java HotSpot(TM) Server VM warning: time warp: -953422407 to 269


Problem analysis results:

1. I was able to get this assertion only on RHEL 4.0 (no assertion on SuSe10)

2. It looks like the assertion was raised either from
     share/vm/memory/generation.hpp:379
   or from
     share/vm/memory/referenceProcessor.cpp:108

   Also, it seems that
     warning("time warp: %d to %d", clock, now);
   should be changed to
     warning("time warp: %lld to %lld", clock, now);

3. Also, this test runs TOO slowly on em64t-002.SFBay.Sun.COM (40 minutes)
   (but this is probably another bug)