[lkml]   [2006]   [Feb]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] x86_64 stack trace cleanup
    On Friday 24 February 2006 12:29, Andres Salomon wrote:

    > That would be nice. Unfortunately, I'm trying to figure out why my dual
    > opteron box likes to push the load up to 15 and then hang while doing
    > i/o to the 3ware 9500S-8 card. Looks like the load/d-state processes
    > are caused by a whole lot (well, MAX_PDFLUSH_THREADS) of pdflush
    > processes spinning on base->lock in lock_timer_base(); not sure if
    > that's intentional or not, but it seems rather odd. Whether the hanging
    > is related to the high load remains to be seen.

    Sounds like some timer handler is broken. You have to find out which
    one it is.

    > I don't see why this is a problem. Other architectures have done this
    > for ages, without problems. I suspect most people get their backtraces
    > from either serial console or logs, as copying them down from the screen
    > or taking a picture of the panic is a rather large pain. It seems like
    > you're penalizing everyone for a few select use cases.

    People submitting jpegs of photographed oopses or even badly scribbled
    down oopses is quite common. Serial consoles are only used by a small

    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-02-24 13:24    [W:0.022 / U:0.212 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site