[lkml]   [2005]   [Dec]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: tsc clock issues with dual core and question about irq balancing
On Mon, 2005-12-12 at 23:26 -0800, Adrian Yee wrote:
> I've been having tsc issues where it counts back occasionally causing
> things like ping to break with errors: "Warning: time of day goes back
> (-1451987us), taking countermeasures." It seems related to
> , but that bug seems to
> be closed (and more x86_64 related). I also get other timing issues
> like single clicks registering as double clicks, and at times double
> clicks that don't register. In addition, if I stress the system with
> something like prime95, then after about 2 minutes the system clock will
> speed up where the clock advances by minutes every second. As suggested
> in bug 5105, I switched to use the pmtimer (clock=pmtmr, my system
> doesn't seem to support hpet) and it has fixed the ping and clock issue,
> but my system doesn't 'feel' right. For example, ssh'ing out of the
> machine is fine, but when ssh'ing into the system a dmesg is very slow
> (spurts out a few pages then pauses for 10-20 seconds, then repeat).
> Also, general desktop usage seems a little sluggish and not what a smp
> system should feel like.

I can't speak about the irq routing issue, but I'm interested in your
issues with the ACPI PM timer.

> I'm currently running an i386 (ie. not x86_64) 2.6.15-rc5 kernel w/ SMP,
> APIC and ACPI enabled (AMD Cool & Quiet disabled), an Athlon 64 X2 3800+
> and EVGA nForce4 SLI (NF41) motherboard. I previously had the processor
> running on an Abit AV8 (K8T800 Pro chipset) board and was having similar
> issues, so it seems to be a dual core issue. I'd just like to add that
> I'm currently testing the system with "nosmp noapic acpi=off clock=tsc"
> (it was losing interrupts and wouldn't boot properly with apic/acpi on)
> and so far everything seems to work (this includes ssh and desktop usage
> is better).

So keeping the above settings, does removing just the "clock=tsc" cause
the sluggishness to appear?

The TSC is *much* faster then the ACPI PM, however it is just not usable
for reliable timekeeping on many SMP systems. That said, the ACPI PM
should not cause performance issues unless you are constantly calling

Also would you open a bugzilla bug on this and attach your .config and


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-12-14 02:07    [W:0.066 / U:1.668 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site