similar to: Strange messages after installing Quad-core processor

It''s everytime when cpufreq_ondemand or cpufreq-set changes the frequency, aprox. 3 messages per event. Is that occasional? I tend to say: no. Please see an excerpt below. And if it''s not occasional, what could I do? And by the way: I found no code that TSC will get adjusted, so I think it will get worse over the time... Thanks, Carsten. messages.0:Jan 9 12:25:15 data kernel:

I have problems to get Xen 3.0 working on my notebook (FSC AMILO Pro V3205). I already used different operating systems for the xen0 domain, like FC5, SUSE 10.1 und Debian SID (2.6.16-2-xen-smp) but i always run into the same trouble. When I try to start a xenU domain it always hangs and I get this: ----------------------------------------------------------------------- debian37:~# xm create

Hi all, We recently upgrade from CentOS 5.8 to CentOS 5.9 on kernel-xen-2.6.18-348.3.1.el5, and after booting into the new kernel, noted large amounts of these messages every second or so in the logs: Mar 30 21:38:35 atlas2 kernel: Warning Timer ISR/0: Time went backwards: delta=-1393683849 delta_cpu=22316151 shadow=225003685197135 off=129240997 processed=225005208029053

I''ve been looking into bug [1]#195 and I have a couple of questions on how timer interrupts and virqs are handled. Is it possible for dom0 linux to irq balance timer interrupts to different cpus? That is, if xen sends a VIRQ_TIMER to vcpu0, backed by cpu0, is it possible for that interrupt to be handled by vcpu1, backed by cpu1 ? After putting in some debug code in to timer_interrupt

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