lkml.org 
[lkml]   [2007]   [Nov]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [stable] Soft lockups since stable kernel upgrade to 2.6.23.8

    * Jeremy Fitzhardinge <jeremy@goop.org> wrote:

    > Greg KH wrote:
    > > Can you try applying the patch below to see if that solves the problem
    > > for you?
    > >
    >
    > I don't think this patch will help; it only has cosmetic changes in
    > addition to the original message printing fix. I think it also needs
    > change a3b13c23f186ecb57204580cc1f2dbe9c284953a:
    >
    > diff -r 79f0ea1e0e70 -r 06f060ab58aa kernel/softlockup.c

    yes, it does need the cpu_clock() changes as i mentioned.

    commit a3b13c23f186ecb57204580cc1f2dbe9c284953a
    Author: Ingo Molnar <mingo@elte.hu>
    Date: Tue Oct 16 23:26:06 2007 -0700

    softlockup: use cpu_clock() instead of sched_clock()

    sched_clock() is not a reliable time-source, use cpu_clock() instead.

    but we only have cpu_clock() from v2.6.23 onwards - so we should not
    apply the original patch to v2.6.22. (we should not have applied your
    patch that started the mess to begin with - but that's another matter.)

    Ingo
    -
    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-11-20 07:09    [W:0.034 / U:30.112 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site