lkml.org 
[lkml]   [2007]   [Jul]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: 2.6.21.5 june 30th to july 1st date hang?
    From
    Date
    On Thu, 2007-07-05 at 15:02 -0600, Chris Friesen wrote:
    > Thomas Gleixner wrote:
    >
    > > It only happens with CONFIG_HIGHRES_TIMERS=y otherwise clock_was_set()
    > > is a NOP. So only the 2.6.21 kernel and i386 and ARM are affected.
    >
    > Are you certain?

    At least for anything >= 2.6.16

    > Vanilla 2.6.10 shows a clock_was_set() function. Does it just not call
    > the dangerous code or something?

    Ouch, the old posix timer code might be affected as well, but I did not
    look.

    > Also, our modified 2.6.10 has the high res timers patch applied, but the
    > config option is turned off and we were still affected.

    You mean Anzingers high res patches. No idea about those.

    tglx


    -
    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/

    \
     
     \ /
      Last update: 2007-07-05 23:21    [W:0.020 / U:0.144 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site