lkml.org 
[lkml]   [2004]   [Oct]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [2.4] 0-order allocation failed
    On Thu, Oct 07, 2004 at 01:18:13PM +0200, Michael Buesch wrote:
    > Hi all,
    >
    > I'm running 2.4.28 bk snapshot of 2004.09.03
    > The machine has an uptime of 7 days, 23:46 now.
    >
    > I was running several bittorrent clients inside of
    > a screen session. Suddenly they all died (including the
    > screen session).
    > dmesg sayed this:
    >
    > __alloc_pages: 0-order allocation failed (gfp=0x1f0/0)
    > __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
    > VM: killing process python
    > __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
    > __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
    > VM: killing process screen
    >
    > I already got this with kernel 2.4.27 vanilla after a
    > higher amount of uptime (I think it was over 10 days).
    > This was exactly the reason I updated to bk snapshot.
    >
    > What can be the reason for this? Is it OOM? (I can't
    > really believe it is).

    Can you check how much swap space is there available when
    the OOM killer trigger? I bet this is the case.

    If its not, we have a problem.

    > Is it a kernel memory leak?
    >
    > With 2.4.26 I never got these errors. And I ran uptimes
    > up to 50 days.
    -
    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: 2005-03-22 14:06    [W:0.033 / U:92.048 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site