[lkml]   [2006]   [Oct]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [patch 00/22] high resolution timers / dynamic ticks - V3

    * Andrew Morton <> wrote:

    > With CONFIG_HIGH_RES_TIMERS=y, CONFIG_NO_HZ=n it's pretty sick. It
    > pauses for several seconds after "input: AlpsPS/2 ALPS GlidePoint as
    > /class/input/input2" (printk-time claims 2 seconds, but it was longer
    > than that).
    > It's been stuck for a minute or more at the 12.980000 time, seems to
    > have hung. The cursor is flashing extremely slowly.

    ah, that's still the VAIO, right? Do you get a 'slow' LOC count on
    /proc/interrupts even on a stock kernel? If yes then that's a
    fundamentally sick local APIC timer interrupt. Stock kernel should show
    sickness too, if for example you boot an SMP kernel on it - can you
    confirm that? (the UP-IOAPIC only relies for profiling on the lapic
    timer, so there the only sickness you should see on the stock kernel is
    a non-working readprofile)

    We'll figure out a way to detect this hardware sickness (which is
    unrelated to our patchset), for now your workaround is either to turn
    off local-apic-timer support (either in the config or on the kernel
    bootline, in which case the high-res code will fall back to the PIT), or
    to turn off high-res timers (either in the config or on the kernel

    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: 2006-10-05 10:27    [W:0.021 / U:0.992 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site