Messages in this thread | | | Date | Mon, 30 Oct 2006 18:41:55 -0800 | From | "Siddha, Suresh B" <> | Subject | Re: AMD X2 unsynced TSC fix? |
| |
On Tue, Oct 31, 2006 at 12:03:28AM +0000, Sergio Monteiro Basto wrote: > time.c: Lost 300 timer tick(s)! rip mwait_idle+0x33/0x4f) > time.c: Lost 300 timer tick(s)! rip mwait_idle+0x33/0x4f) > time.c: Lost 300 timer tick(s)! rip mwait_idle+0x33/0x4f) > time.c: Lost 300 timer tick(s)! rip mwait_idle+0x33/0x4f)
Is this the reason why you are saying your system has unsynchronized TSC? Some where in this thread, you mentioned that Lost ticks happen even when you use "notsc"
This sounds to me as a different problem. Can you send us the output of /proc/interrupts?
thanks, suresh - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |