[lkml]   [2007]   [Jul]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: june 30th to july 1st date hang?
    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

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


    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: 2007-07-05 23:21    [W:0.018 / U:24.008 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site