similar to: Timer ISR: Timer went backwards [NetBSD 3.1 / Xen 2.0.7]

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.

Hai, ? Can somebody try to run : ? samba-tool time and samba-tool time servername.fqdn ? when i run it, im getting : ? ERROR(runtime): uncaught exception - Connection to SRVSVC pipe of server 'rotterdam.bazuin.nl' failed: NT_STATUS_NONE_MAPPED ? File "/usr/lib/python2.7/dist-packages/samba/netcmd/__init__.py", line 175, in _run ??? return self.run(*args, **kwargs) ? File

Hi all, Using a slow serial console with sync_console on SMP leaves me with an unusable system: it gets into a flood of Timer ISR/0: Time went backwards: delta=-3566279 cpu_delta=16433721 shadow=2019998373 off=420435384 processed=2444000000 cpu_processed=2424000000 0: 2424000000 1: 2444000000 messages which swamps the console and leaves things almost, but not quite, completely hung. It is a

On 27/02/15 11:45, L.P.H. van Belle wrote: > Ok.. very strange .. > > for me : > ERROR(runtime): uncaught exception - Connection to SRVSVC pipe of server 'internal.domain.tld' failed: NT_STATUS_NONE_MAPPED > > for peter: > one works, one : > ERROR(runtime): uncaught exception - Connection to SRVSVC pipe of server 'ulysses.home.serbe.ch' failed:

All, Attached is a patch from Prarit Bhargava, who is not subscribed to the list (but CC''ed). His description follows: Add "Warning" to the "Time went backwards" message. Most QA groups (if not all) grep for specific messages in the syslog such as "Error", "Warning", "Oops". Time went backwards is a key error which can result in

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:

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

>I''ve been seeing these pretty regularly on a single-socket dual-core Athlon >system for the last couple of months, and only on Friday finally found time >to start looking into these. Besides the messages above, I also see hangs >in about every other boot attempt but only if I do *not* use serial output >(which makes debugging a little harder), and never once initial boot

Hello! I am encountering a problem with one of the machines I am using and the timer going backwards. It looks like the problem is due to to a bad PM-Timer entry being found. Though when debugging further, the real source of the problem stems from an ACPI table of type DSDT being parsed as an FADT during boot and certainly a bogus PM-Timer is found there. Here''s the output from

Hi, using SLES10 I''m unable to synchronize the time of DomU with that of Dom0. There is a persistent offset of about 3 seconds! Here''s a small history (not actual output): remote refid st t when poll reach delay offset jitter rkdvmso1.dvm.kl 192.168.0.11 5 u - 64 1 0.136 -2977.1 0.099 *rkdvmso1.dvm.kl 192.168.0.11 5 u 2 64

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, 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

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 good people, can someone direct me to a solution, I get the following error. # xm create -c vm03 Using config file "./vm03". Error: (2, 'Invalid kernel', 'xc_dom_compat_check: guest type xen-3.0-x86_32 not supported by xen kernel, sorry\n') Here is my config file kernel="/boot/netbsd/netbsd-INSTALL_XEN3_DOMU.gz" (Download from amd64) name =

Hi all, please direct me to NetBSD install file or FreeBSD to install on Xen 3.1 on (CentOS 5.2) Thanks, - Augustin -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20080813/428a4792/attachment-0004.html>

Hello, I'm trying to get Super MNC running under Wine with Steam, I can start the game up perfectly fine and join training matches with other players, but I can't join a non-training match, when I try to it puts me in a queue which I never leave. Here's the ouput which includes Steam's output also: http://pastebin.com/LDTEgbZz Thanks.

On Sun, Jul 13, 2014 at 10:26 PM, H. Peter Anvin <hpa at zytor.com> wrote: > On 07/13/2014 10:54 AM, syslinux-bot for Gene Cumm wrote: >> Commit-ID: 3741886cb700e1017d70f1753f013fa10f4d9272 >> Gitweb: http://www.syslinux.org/commit/3741886cb700e1017d70f1753f013fa10f4d9272 >> Author: Gene Cumm <gene.cumm at gmail.com> >> AuthorDate: Sun, 13 Jul 2014

Hi all, Based on the commitdiff comments, this looks like what I (and many many others) have been plagued with. Machines typically affected: DELL PowerEdge 2950, R720, R810, etc. (server class) DELL PowerEdge 960 (desktop class) Eagerly awaiting the next pre-release to test this out! : thumbs up : : thumbs up : Regards, Shantanu