Messages in this thread | | | Subject | Re: AMD X2 unsynced TSC fix? | From | Sergio Monteiro Basto <> | Date | Tue, 31 Oct 2006 15:05:04 +0000 |
| |
On Mon, 2006-10-30 at 18:41 -0800, Siddha, Suresh B wrote: > 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?
yes
> Some where in this thread, you mentioned that Lost ticks happen even > when you use "notsc"
yes, with news kernels 2.6.19-rcx
> > This sounds to me as a different problem. Can you send us the output > of /proc/interrupts?
of which kernel ? I am not at home .. but I have here /proc/interrupts from one 2.6.16 http://bugzilla.kernel.org/attachment.cgi?id=7927&action=view from my bug http://bugzilla.kernel.org/show_bug.cgi?id=6419
Tonight I can attach on bugzilla bug#6419, /proc/interrupts from one kernel 2.6.18 and from one kernel 2.6.19-rc4
BTW: those kernels are for x86_64 arch, I haven't try, yet, i386, but maybe will be my next test.
Thanks, -- Sérgio M. B. > > 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/
| |