Re: kswapd in tight loop 2.6.9-rc3-bk-recent

From: Nick Piggin (piggin_at_cyberone.com.au)
Date: 10/08/04

  • Next message: blaisorblade_spam_at_yahoo.it: "[patch 1/2] uml: fix fd leak with HostFs" 
    Date:	Fri, 08 Oct 2004 13:13:16 +1000
To: Andrew Morton <akpm@osdl.org>

    Andrew Morton wrote:

    >Nick Piggin <piggin@cyberone.com.au> wrote:
    >
    >>>Chris Wright <chrisw@osdl.org> wrote:
    >>>
    >> >
    >> >>(whereas I could get the mainline code, and the
    >> >> one-liner to spin right off).
    >> >>
    >> >
    >> >How? (up to and including .config please).
    >> >
    >> >
    >> >
    >>
    >> Ah, free_pages <= pages_high, ie. 0 <= 0, which is true;
    >> commence spinning.
    >>
    >
    >Maybe. It requires that the zonelists be screwy:
    >
    > Node 1 DMA free:0kB min:0kB low:0kB high:0kB active:0kB inactive:0kB present:0kB
    > protections[]: 0 0 0
    > Node 1 Normal free:25272kB min:1020kB low:2040kB high:3060kB active:624172kB inactive:282700kB present:1047936kB
    > protections[]: 0 0 0
    > Node 1 HighMem free:0kB min:128kB low:256kB high:384kB active:0kB inactive:0kB present:0kB
    > protections[]: 0 0 0
    > Node 0 DMA free:728kB min:12kB low:24kB high:36kB active:788kB inactive:7848kB present:16384kB
    > protections[]: 0 0 0
    > Node 0 Normal free:27200kB min:1004kB low:2008kB high:3012kB active:332792kB inactive:422744kB present:1032188kB
    > protections[]: 0 0 0
    > Node 0 HighMem free:0kB min:128kB low:256kB high:384kB active:0kB inactive:0kB present:0kB
    > protections[]: 0 0 0
    >
    >See that DMA zone on node 1? Wonder how it got like that. It
    >should not be inside pgdat->nrzones anyway.
    >
    >
    Oh? Why not? I didn't think empty zones were filtered out? (perhaps
    they should be).

    >David, is your setup NUMA? Can you show us a sysrq-M dump?
    >
    >

    Yes. Incase he's alseep, I'll quote:

    "I saw the same thing yesterday, also on an amd64 box though that
    could be coincidence. The kswapd1 process was pegging the cpu at 99%
    kswapd0 was idle. After a few minutes, the box became so unresponsive"

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

  • Next message: blaisorblade_spam_at_yahoo.it: "[patch 1/2] uml: fix fd leak with HostFs"

    Relevant Pages

    • Re: kswapd in tight loop 2.6.9-rc3-bk-recent
      ... It requires that the zonelists be screwy: ... See that DMA zone on node 1? ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [discuss] Re: x86_64: 2.6.14-rc4 swiotlb broken
      ... goal to avoid 16MB DMA zone. ... Statically reserve bounce buffer space and initialize bounce buffer data ... panic("Cannot allocate SWIOTLB buffer"); ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: oom killer gone nuts
      ... > didn't look so much out of DMA zone, there's 4M of ram free. ... I've added all 6 of the OOM patches (I didn't notice that thread until ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: oom killer gone nuts
      ... This was a GFP_KERNEL|GFP_DMA allocation triggering this. ... didn't look so much out of DMA zone, there's 4M of ram free. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)