similar to: [PATCH]: Add "Warning" to the time went backwards messages

I have a high end IBM system with 4 HT CPUs, am running xen-unstable with only Dom0 active, and I get lots of "Timer ISR/n: Time went backwards" messages. This is a short segment from dmesg: Timer ISR/1: Time went backwards: -259000 4465110000000 9741000 4465120000000 Timer ISR/6: Time went backwards: -224000 4465110000000 9776000 4465120000000 Timer ISR/6: Time went backwards: -159000

In 780427f0e11 (Indicate that clock was set in the pvclock gtod notifier), logic was added to pass a CLOCK_WAS_SET notification to the pvclock notifier chain. While that patch added a action flag returned from accumulate_nsecs_to_secs(), it only uses the returned value in one location, and not in the logarithmic accumulation. This means if a leap second triggered during the logarithmic

In 780427f0e11 (Indicate that clock was set in the pvclock gtod notifier), logic was added to pass a CLOCK_WAS_SET notification to the pvclock notifier chain. While that patch added a action flag returned from accumulate_nsecs_to_secs(), it only uses the returned value in one location, and not in the logarithmic accumulation. This means if a leap second triggered during the logarithmic

Changeset 6902 Sep 18 13:37:23 inyoureyes kernel: 1: 5077390000000 Sep 18 13:37:23 inyoureyes kernel: Timer ISR/1: Time went backwards: delta=-34786504 cpu_delta=15257914 shadow=5076506780929 off=938478409 processed=50770Sep 18 13:37:23 inyoureyes kernel: 0: 5077480044418 Sep 18 13:37:23 inyoureyes kernel: 1: 5077430000000 Sep 18 13:37:23 inyoureyes kernel: Timer ISR/1: Time went backwards:

Hello, I have recently finally gotten xen working on a Dual Core Althlon64 4200, 4GB RAM, 3ware 9500 4x160GB SATA RAID 10, but after compiling xen with 3ware support, xen does start up but i get many (to many to even access the console) of these errors: Time ISR: Time went backwards: -xxxxxxxx xxxxxxxxxxxx xxxxx xxxxxxxxx where the x''s are replaced with different numbers each time.

I continue to see occasional ''time went backwards'' messages on 3.0-testing on larger systems. Is anyone else seeing such? Have there been any improvements to -unstable that haven''t been moved over? If so, can anyone point out the respective changesets? Thanks, Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Hello gurus, I have two physical xen hosts and when I migrate a domU from one host to another, I get many of this error from domU kernel: clocksource/0: Time went backwards: delta=-3536123661 shadow=686019823475 offset=281887188 Sometimes domU time stalls and network stops working, but other times it gets working again. The two hosts are using different platform timer source:

Hi, all -- I''m in the process of configuring a new machine for use as a Xen server, and am having some rather significant stability issues. The hardware/distro/kernel info is: opensuse 10.3 Linux offxen2 2.6.22.5-31-xen #1 SMP 2007/09/21 22:29:00 UTC x86_64 x86_64 x86_64 GNU/Linux 2 x Dual-Core AMD Opteron(tm) Processor 2212 HE 8 x 2GB PC2-5300 RAM Xen 3.1.0_15042-51 I currently have

Hi Ingo, This series of patches implements a number of improvements to the softlockup watchdog and its users. They are: 1. Make the watchdog ignore stolen time When running under a hypervisor, the kernel may lose an arbitrary amount of time as "stolen time". This may cause the softlockup watchdog to trigger spruiously. Xen and VMI implement sched_clock() as measuring unstolen time,

Hi Ingo, This series of patches implements a number of improvements to the softlockup watchdog and its users. They are: 1. Make the watchdog ignore stolen time When running under a hypervisor, the kernel may lose an arbitrary amount of time as "stolen time". This may cause the softlockup watchdog to trigger spruiously. Xen and VMI implement sched_clock() as measuring unstolen time,

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

Dear fellow Xen''ers! I''m having a problem with my new Xen-enabled colocation server.. I hope ( at least ;) ) one of you guys know how to fix this problem.. For a certain amount of time ( 1-2 days ) the domU runs fine.. until the console starts spitting out messages like these: [80182.004456] clocksource/0: Time went backwards: delta=-6917292717540055641 shadow=80182004054805

Hi All, I''m new to Xen and... Happy New Year! After restarting dom-0, my dom-u prints this in console once every second, [55082.616234] __ratelimit: 1503 messages suppressed [55082.616234] clocksource/0: Time went backwards: ret=380ab26c53a I resolved this by following the instructions in "http://wiki.debian.org/Xen", which is basically changing clocksource to

Hi I don't know where the announcements go. I cloned https://git.centos.org/git/rpms/kernel.git and grabbed the changelog section pasted below from the git diff in SPECS/kernel.spec (commit dated 4 Feb 2020) Regards +* Thu Dec 12 2019 Frantisek Hrbata <fhrbata at hrbata.com> [3.10.0-1062.12.1.el7] +- [powerpc] powerpc/pseries: Remove confusing warning message (Gustavo Duarte) [1780148

Hi there, I am having the problems described in bug 195 with the current hg nstable tree on amd64 (Athlon64, single core). Is anyone working on that issue? Thanks in andvance, Johnny -- jabber:johnny@wh-netz.de icq:236971856 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hello, I am experiencing a number of 'Time moved backwards errors' such as: Mar 27 11:38:20 host-78-129-239-60 dovecot: imap-login: Time just moved backwards by 729 seconds. This might cause a lot of problems, so I'll just kill myself now. http://wiki.dovecot.org/TimeMovedBackwards Mar 27 15:20:10 host-78-129-239-60 dovecot: Time just moved backwards by 4214 seconds. This might cause

Hi all, I am running dovecot version 1.1.1 (dovecot --version) and keeps to have time moved backwards problem. I first found dovecot dead without obvious error message, but see the following when restart dovecot service by # service dovecot restart >Stopping Dovecot Imap: [FAILED] >Starting Dovecot Imap: Warning: Last died with error (see error log for more information): Time

OK.. So I synced the clock.... and got .... dovecot: Time just moved backwards by 1 seconds. I'll sleep now until we're back in present. http://wiki.dovecot.org/TimeMovedBackwards ( The first time I did this the clock moved backwards 2 hours after a timezone change and dovecot suicided ) I think I understand the concept ... However a mail server should probably be synchronized to the

i've dovecot --version 1.2.5 hg log | grep changeset | head -n 1 changeset: 9407:a3e16df805e3 in my logs, i'm seeing ... Oct 05 16:51:40 dovecot: Error: Time just moved backwards by 1 seconds. I'll sleep now until we're back in present. http://wiki.dovecot.org/TimeMovedBackwards Oct 05 17:07:22 dovecot: Error: Time just moved backwards by 1 seconds. I'll sleep now

I'm running dovecot on an OpenBSD 3.7 server and after upgrading to RC25, the daemon started exiting with: Fatal: Time just moved backwards (1173221579 -> 1173221578)! This might cause a lot of problems, so I'll just kill myself now. After upgrading to RC26, I've gotten the error: Error: Time just moved backwards by 1 seconds. I'll sleep now until we're back in