Time stopped

[David F Barrera <dfbp@us.ibm.com>]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=265

While running xm-test on two IBM xSeries 335s, one FC4 and the other one
SLES 9, I noticed that time has stopped:

[root@x335a xm-test]# date
Wed Sep 28 13:59:18 CDT 2005
[root@x335a xm-test]# date
Wed Sep 28 13:59:18 CDT 2005

>> 15 minutes later,
[root@x335a xm-test]# date
Wed Sep 28 13:59:18 CDT 2005
[root@x335a xm-test]#

changeset:   7076:46046d5fb354
tag:         tip
user:        emellor@ewan
date:        Tue Sep 27 16:09:46 2005 +0100
summary:     Remove unused import, mark unused variables.

The last output lines produced by xm-test are:
cp 06_destroy_dom0_neg.py 06_destroy_dom0_neg.test
chmod +x 06_destroy_dom0_neg.test

The machines in question are running xm-test at the moment and appear
'stuck'.
Both are displaying the "(XEN) Ouch! We are seriously BEHIND schedule!"
messages. However, the static time issue may not be related to the Ouch!
issue, bug # 257, as Paul Larson observed it on a machine that was not
running xm-test at the time, hence we are submitting it as a different
bug.


-- 
Regards,

David F Barrera
Linux Technology Center
Systems and Technology Group, IBM

"The wisest men follow their own direction. "
                                                        Euripides