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

[Xen-devel] Time went backwards 885 ms


  • To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Carsten Schiers <carsten@xxxxxxxxxx>
  • Date: Fri, 27 Mar 2009 10:18:37 +0100
  • Delivery-date: Fri, 27 Mar 2009 02:19:28 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Dear all,

I thought this might be worth again to report:

After rebooting a 3.3.1/2.6.18.8 environment on my AMD 4050e, I received a 885ms delta just
after powernow-k8 loaded:

Mar 26 21:28:37 data kernel: powernow-k8: Found 2 AMD Athlon(tm) Dual Core Processor 4050e processors (version 2.20.00)
Mar 26 21:28:37 data kernel: powernow-k8:    0 : fid 0xd (2100 MHz), vid 0xe
Mar 26 21:28:37 data kernel: powernow-k8:    1 : fid 0xc (2000 MHz), vid 0xf
Mar 26 21:28:37 data kernel: powernow-k8:    2 : fid 0xa (1800 MHz), vid 0x11
Mar 26 21:28:37 data kernel: powernow-k8:    3 : fid 0x2 (1000 MHz), vid 0x16
Mar 26 21:28:37 data kernel: Timer ISR/1: Time went backwards: delta=-885437842 delta_cpu=6562158 shadow=11822142480 off=436198 processed=12708016520 cpu_p
rocessed=11816016520
Mar 26 21:28:37 data kernel:  0: 12704016520
Mar 26 21:28:37 data kernel:  1: 11816016520

Find full xm dmesg, xm info, and syslog of boot attached.

Otherwise, the environment is more stable; Time went backwards appear roughly every 2-3 days,
mostly when there is a 1,0->2,1GHz jump when munin asks for CPU. It is reduced in addition by a
4 sec sampling time of the ondemand govenor.

Will test 3.4 as soon as released.

BR,
Carsten.


Attachment: syslog.txt
Description: Text document

Attachment: xmdmesg.txt
Description: Text document

Attachment: xminfo.txt
Description: Text document

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

 


Rackspace

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