I know this has been gone over before, and I am aware of the possible
fix being the use of the pmtmr.
My question is, if there is support builtin to the kernel for more than
one timer, and we know that no timer but the pmtimer is reliable on a
dual core system, why doesn't the startup of the kernel choose the
pmtimer based on if it detects the system is a dual core proc with smp
enabled? And if the pmtimer doesn't fix this sync issue, is there a
fix out there? Currently with 2.6.16-rc1-mm5 the non-customized boot
args to the kernel results in these messages.
Losing some ticks... checking if CPU frequency changed.
warning: many lost ticks.
Your time source seems to be instable or some driver is hogging interupts
rip default_idle+0x2d/0x60
cpufreq is enabled of course.
-
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]
