search for: cpu_delta

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: delta=-19106454 cpu_delta=50937964 shadow=5076506780929 off=98415...

...t in linux, I can see that when we get a "Time went backwards" message, that shadow->system_timestamp+offset is significantly behind the previous value of processed_system_time, and that the previous value was set by the OTHER vcpu. Timer ISR/0: Time went backwards: delta=-44611438 cpu_delta=15388562 shadow=69081255546 off=254172405 processed=69380039389 cpu_processed=69320039389 last_modified=CPU1, prev_st=69291796314, prev_offset=92519230 0: 69320039389 1: 69380000000 Timer ISR/0: Time went backwards: delta=-1374402 cpu_delta=528625598 shadow=69081255546 off=777409441 processed=698...

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 simple matter to ratelimit these printks, which completely eliminates the proble...

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