[lkml]   [2005]   [Oct]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: clock skew on B/W G3


    given that this option causes problems on non i386 systems, may I propose to
    mark CONFIG_HZ as broken on these architectures and/or use a default value of
    1000 ? I guess this issue can't be fixed in a sane way until 2.6.14 is out.


    Le Montag 03 Oktober 2005 16:18, Rune Torgersen a écrit :
    > > -----Original Message-----
    > > From: Marc
    > > Sent: Sunday, October 02, 2005 11:46
    > >
    > > Some additions to the previous mail: I was able to isolate
    > > the problem to the
    > > introduction of a user specificable value of HZ (in
    > > include/asm-ppc/parm.h).
    > > I used a value of 250 while the former default was 1000.
    > > Setting it back to
    > > 1000 makes the clock tick right again.
    > >
    > > Is the CONFIG_HZ known to be broken on PPC ?
    > CONFIG_HZ is not broken, but the whole clock configuration is.
    > (I poseded something about it for 8260 earlier this summer)
    > Basic problem is that CLOCK_TICK_RATE which is used for setting up the
    > variables used for advancing the clock, is hardcoded to a value that
    > only makes sence for an i386. (it is default set at 1193180Hz which
    > happens to be the timer clock for timer1 on an i386 machine)
    > Another problem here is that that value apparently hve to be #define'd
    > which means you cannot insert the decrementer frequency from the
    > boot-loader either.
    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-10-04 08:17    [W:0.021 / U:10.032 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site