Xen users - May 2007 - Timer ISR: Timer went backwards [NetBSD 3.1 / Xen 2.0.7]

I''m using a NetBSD 3.1 dom0 with Xen 2.0.7 (so far as I know, the
latest
supported combination for the NetBSD platform).

Linux domUs have their logs fill with messages like this:

May  8 02:01:39 debian kernel: Timer ISR: Time went backwards: -316000 
131542680000000 9684000 131542690000000
May  8 02:01:39 debian kernel: Timer ISR: Time went backwards: -277000 
131542680000000 9723000 131542690000000

They come in different amounts, sometimes a handful, sometimes hundreds. 
Over the space of a day or two, the logs swell to gigantic sizes.

I have been googling this for a while and it seems like I am the only 
person in the universe to experience this after 2005. So apparently time 
really has gone backwards - about two years'' worth.

Back in 2005, one of the people experiencing the problem was asked to 
provide the output of ''xm dmesg | grep timer''. However, when I
try ''xm
dmesg'', I just get ''Error: Internal Server Error'',
which doesn''t seem like
a good sign. Is it?

Someone was also asked to provide the contents of /proc/interrupts from a 
domU, here it is:

debian:~# cat /proc/interrupts
            CPU0
128:          1     Dynamic-irq  misdirect
129:       1394     Dynamic-irq  ctrl-if
130:   89007332     Dynamic-irq  timer
131:        803     Dynamic-irq  blkif
132:       3782     Dynamic-irq  eth0
NMI:          0
ERR:          0

For the domUs I am using the vmlinuz-2.6.11.12-xenU kernel found on the 
Xen web site.

Does anyone have any ideas? I really hope I can get this to work.

miguel

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Hello Miguel,

I think I have the same or a similar problem:
My kernel clocks (Dom0 and DomU) are a bit too slow (about 10%: a
clock-minute takes about 66 real seconds). But my Kernel (suse 10.2)
does not tell me something like "Time went backwards" - but my lirc
daemon does...

Just like you described, this doesn''t happen constantly: Somethimes it
is ok, sometimes its worse.

I "solved" this problem with a cron-entry "-* * * * *     
ntpdate
ptbtime1.ptb.de >/dev/null".
This helps but really isn''t nice and I am waiting for the day where
this
is not ok...


Dirk


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users