Re: AMD X2 unsynced TSC fix?

On Wed, Nov 01, 2006 at 01:46:48AM +0000, Sergio Monteiro Basto wrote:
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?
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?

/proc/interrupts on kernel 2.6.18
http://bugzilla.kernel.org/attachment.cgi?id=9384&action=view
dmesg w/o notsc kernel 2.6.19-rc4
http://bugzilla.kernel.org/attachment.cgi?id=9385&action=view
/proc/interrupts kernel 2.6.19-rc4
http://bugzilla.kernel.org/attachment.cgi?id=9386&action=view
dmesg w/ notsc kernel 2.6.19-rc4
http://bugzilla.kernel.org/attachment.cgi?id=9387&action=view
/proc/interrupts kernel 2.6.19-rc4
http://bugzilla.kernel.org/attachment.cgi?id=9388&action=view
list of interrupts give by windows XP
http://bugzilla.kernel.org/attachment.cgi?id=9389&action=view

First of all, from "lost timer ticks" messages and the fact that "notsc"
decreases the number of ticks lost can't be concluded as a TSC sync issue.

Some device is hogging interrupts which results in lost timer ticks and from
your 2.6.18 interrupts info, usb seems to be the culprit.. It is probably
a side effect that "notsc" decreases the lost timer ticks..

copied Len who seems to be the owner of the bug for his thoughts..
(http://bugzilla.kernel.org/show_bug.cgi?id=6419)

thanks,
suresh
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Corrupted/lost MS audio drivers, error code 39 in device manager
    ... The other week my PC had a spell of rebooting itself and performing a scandisk each time, and some allocation units were lost. ... MS Kernel Wave Audio Mixer, MS Kernel DLS Synthesizer & MS Kernel DRM Audio Descrambler. ... Following the XP Toubleshooter's advice and trying to uninstall and reinstall the driver has the PC automatically looking for a driver and saying there is nothing better than the existing one! ...
    (microsoft.public.windowsxp.perform_maintain)
  • Re: Kernel Timeslice
    ... I would like the kernel ... Right now I think it is set for 100 ticks ... I would expect them to be over 1000 under load, indicating that something else is limiting response. ... area, I found major changes in that area, and traded a small bit of total performance for far more response. ...
    (Fedora)
  • Re: [PATCH 0/2] itimers: periodic timers fixes
    ... So 10 ticks would take only about ... the kernel decides it must never return earlier than ... a systematic multiplicative timing error of -10 %. ... changing all the sampling from cputime to ktime_t is ...
    (Linux-Kernel)
  • Re: [PATCH 0/2] itimers: periodic timers fixes
    ... So 10 ticks would take only about ... the kernel decides it must never return earlier than ... a systematic multiplicative timing error of -10 %. ... changing all the sampling from cputime to ktime_t is ...
    (Linux-Kernel)
  • [PATCH 6/9] handle lost timer ticks in ptimer
    ... This changes how ptimer deals with lost timer ticks (as far as they can be ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)