[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] repeatable time jump



" linux-2.6.8.1-xen-sparse/arch/xen/i386/kernel/time.c and see what
" comes out when you run your test. It's also interesting to see
" what output comes out after the time skip whenever you run date. 

OK, I pulled and patched.   I ran date in a loop as xenU was shutdown
and time jumped 4293 secs from 1096637912.846396000 to 1096642205.961018000
ntpd was running in xen0.

The console is getting continuous Clamp messages.  The xen0 Syslog says:

Oct  1 09:34:44 rack043-xen kernel: device eth0 entered promiscuous mode
Oct  1 09:34:44 rack043-xen kernel: xen-br0: port 1(eth0) entering learning 
stat e
Oct  1 09:34:44 rack043-xen kernel: xen-br0: topology change detected, 
propagati ng
Oct  1 09:34:44 rack043-xen kernel: xen-br0: port 1(eth0) entering forwarding 
st ate
Oct  1 09:34:44 rack043-xen kernel: Clamp time 1096637684 1096637684
Oct  1 09:36:20 rack043-xen kernel: device vif1.0 entered promiscuous mode
Oct  1 09:36:21 rack043-xen kernel: xen-br0: port 2(vif1.0) entering learning 
st ate
Oct  1 09:36:21 rack043-xen kernel: xen-br0: topology change detected, 
propagati ng
Oct  1 09:36:21 rack043-xen kernel: xen-br0: port 2(vif1.0) entering forwarding 
state
Oct  1 09:37:10 rack043-xen ntpd[838]: synchronized to LOCAL(0), stratum 13
Oct  1 09:37:10 rack043-xen ntpd[838]: kernel time sync disabled 0041
Oct  1 09:38:01 rack043-xen /USR/SBIN/CRON[955]: (mail) CMD (  if [ -x 
/usr/lib/ exim/exim3 -a -f /etc/exim/exim.conf ]; then /usr/lib/exim/exim3 -q ; 
fi)
Oct  1 09:38:16 rack043-xen ntpd[838]: synchronized to 172.16.4.1, stratum 3
Oct  1 09:38:32 rack043-xen kernel: device vif1.0 left promiscuous mode
Oct  1 09:38:32 rack043-xen kernel: xen-br0: port 2(vif1.0) entering disabled st
ate
Oct  1 10:50:05 rack043-xen kernel: xen-br0: port 2(vif1.0) entering disabled st
ate
Oct  1 10:50:06 rack043-xen kernel: Clamp time 1096642206 1096642206
Oct  1 10:50:06 rack043-xen last message repeated 529 times
Oct  1 10:50:06 rack043-xen kernel: Clamp 206
Oct  1 10:50:06 rack043-xen kernel: Clamp time 1096642206 1096642206
Oct  1 10:50:06 rack043-xen last message repeated 112 times
Oct  1 10:50:06 rack043-xen kernel: Clamp time 109664220206
Oct  1 10:50:06 rack043-xen kernel: Clamp time 1096642206 1096642206
Oct  1 10:50:06 rack043-xen last message repeated 112 times
Oct  1 10:50:06 rack043-xen kernel: Clamp time 109664220206
Oct  1 10:50:06 rack043-xen kernel: Clamp time 1096642206 1096642206
Oct  1 10:50:06 rack043-xen last message repeated 112 times
Oct  1 10:50:06 rack043-xen kernel: Clamp time 109664220206
Oct  1 10:50:06 rack043-xen kernel: Clamp time 1096642206 1096642206
Oct  1 10:50:06 rack043-xen last message repeated 112 times
Oct  1 10:50:06 rack043-xen kernel: Clamp time 109664220206
Oct  1 10:50:06 rack043-xen kernel: Clamp time 1096642206 1096642206
Oct  1 10:50:06 rack043-xen last message repeated 112 times
Oct  1 10:50:06 rack043-xen kernel: Clamp time 109664220206
Oct  1 10:50:06 rack043-xen kernel: Clamp time 1096642206 1096642206



If I try xm dmesg at this point, xm hangs.  Looks like it is waiting for
xend to say sometime. After ctrl-C xm says:

rack043-xen:~# xm dmesg
Traceback (most recent call last):
  File "/usr/sbin/xm", line 6, in ?
    main.main(sys.argv)
  File
"/usr/research/playground/becker/xen/obj-unstable/xeno-unstable.bk/install/lib/python/xen/xm/main.py",
line 786, in main
    xm.main(args)
  File
"/usr/research/playground/becker/xen/obj-unstable/xeno-unstable.bk/install/lib/python/xen/xm/main.py",
line 105, in main
    self.main_call(args)
  File
"/usr/research/playground/becker/xen/obj-unstable/xeno-unstable.bk/install/lib/python/xen/xm/main.py",
line 123, in main_call
    p.main(args[1:])
  File
"/usr/research/playground/becker/xen/obj-unstable/xeno-unstable.bk/install/lib/python/xen/xm/main.py",
line 684, in main
    print server.xend_node_dmesg()
  File
"/usr/research/playground/becker/xen/obj-unstable/xeno-unstable.bk/install/lib/python/xen/xend/XendClient.py",
line 183, in xend_node_dmesg
    return self.xendGet(self.nodeurl('dmesg'))
  File
"/usr/research/playground/becker/xen/obj-unstable/xeno-unstable.bk/install/lib/python/xen/xend/XendClient.py",
line 145, in xendGet
    return self.client.xendGet(url, args)
  File
"/usr/research/playground/becker/xen/obj-unstable/xeno-unstable.bk/install/lib/python/xen/xend/XendProtocol.py",
line 68, in xendGet
    return self.xendRequest(url, "GET", args)
  File
"/usr/research/playground/becker/xen/obj-unstable/xeno-unstable.bk/install/lib/python/xen/xend/XendProtocol.py",
line 143, in xendRequest
    resp = conn.getresponse()
  File "/usr/lib/python2.3/httplib.py", line 778, in getresponse
    response.begin()
  File "/usr/lib/python2.3/httplib.py", line 273, in begin
    version, status, reason = self._read_status()
  File "/usr/lib/python2.3/httplib.py", line 231, in _read_status
    line = self.fp.readline()
  File "/usr/lib/python2.3/socket.py", line 323, in readline
    data = recv(1)
KeyboardInterrupt



-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.