Andrew Morton wrote:
Presumably someone is getting a lot of these messages.
Do we know why? Is there something which needs fixing here?
I got it a lot when using any sort of virtualization on my Core2Duo
(kvm, vmware, qemu). Just a big spew. Honestly, I was getting this with
2.6.20, and haven't tested again with latest kernel.
OK, a bit of googling finds things like this:
http://chxo.com/be2/20060821_3333.html, so I assume that it's some sort of
generic problem with the hypervisor's emulation of the RTC.
Zach, do you know what the score is here?
We at least jack up the rtc for fast clock timeouts with better
granularity - so it can be a host kernel issue, although a guest kernel
trying to get high frequency RTC will also be inaccurate, and inevitably
will have unhidable interrupt lateness.
Ratelimiting seems the right thing to do, as once you have noted late
RTC interrupts, it doesn't need to be noted again, and there is nothing
you can do to fix it. It is useful as a warning about interrupt
disabled handlers taking too long, but there are other ways of detecting
that too.
Zach
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
