> > Try running your guest with -no-kvm (and even with the kvm module not
> > loaded, just to be sure). In my case I still saw the messages.
> > However, removing the "-net tap" line from my command line did get rid
> > of the messages.
>
> Hmmm I'm getting the same thing on 2.6.20.1 as wel
> Holding a lock too long should be easy to debug with the -rt patch -
> set the preemption related options to match mainline, and enable the
> latency tracer.
Good idea, I'll give it a shot when I get a chance.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the bo
On 3/8/07, Roland Dreier <[EMAIL PROTECTED]> wrote:
> When ever I try and start a guest OS with kvm I get a lot of these rtc
> missing interupt messages from the kernel
>
> [ 468.510878] rtc: lost some interrupts at 1024Hz.
I started to debug this a little while ago but I never got too far.
I started to debug this a little while ago but I never got too far.
However it doesn't seem connected with kvm -- it is something to do
with tun/tap or bridging holding a lock too long I think.
Try running your guest with -no-kvm (and even with the kvm module not
loaded, just to be sure). In my
> When ever I try and start a guest OS with kvm I get a lot of these rtc
> missing interupt messages from the kernel
>
> [ 468.510878] rtc: lost some interrupts at 1024Hz.
I started to debug this a little while ago but I never got too far.
However it doesn't seem connected with kvm -- it is
When ever I try and start a guest OS with kvm I get a lot of these rtc
missing interupt messages from the kernel
[ 468.510878] rtc: lost some interrupts at 1024Hz.
[ 468.530876] rtc: lost some interrupts at 1024Hz.
[ 468.550868] rtc: lost some interrupts at 1024Hz.
[ 468.570864] rtc: lost som
6 matches
Mail list logo
