public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tommy Wu <tommy@teatime.com.tw>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: Daniel Phillips <phillips@bonn-fries.net>
Subject: Memory Problem in 2.4.9 ?
Date: Wed, 22 Aug 2001 12:47:02 +0800	[thread overview]
Message-ID: <20010822124255.4DEE.TOMMY@teatime.com.tw> (raw)

Hi!

   I've tried the patch in the kernel list. Got the result as following...
   This message for command: 
   dd if=/dev/zero of=test.dmp bs=1000k count=2500
   on a PIII 1G SMP box with 1G RAM (HIGHMEM enabled)
   kernel 2.4.9 with XFS filesystem patch.
   
Aug 22 11:51:04 standby kernel: __alloc_pages: 0-order allocation failed (gfp=0x30/1).
Aug 22 11:51:11 standby last message repeated 111 times
Aug 22 11:51:11 standby kernel: cation failed (gfp=0x30/1).
Aug 22 11:51:11 standby kernel: __alloc_pages: 0-order allocation failed (gfp=0x30/1).
Aug 22 11:51:11 standby last message repeated 281 times
Aug 22 11:51:17 standby kernel: cation failed (gfp=0x30/1).
Aug 22 11:51:17 standby kernel: __alloc_pages: 0-order allocation failed (gfp=0x30/1).
Aug 22 11:51:29 standby last message repeated 315 times
Aug 22 11:51:29 standby kernel: cation failed (gfp=0x30/1).
Aug 22 11:51:29 standby kernel: __alloc_pages: 0-order allocation failed (gfp=0x30/1).
Aug 22 11:51:29 standby last message repeated 281 times
Aug 22 11:52:21 standby last message repeated 43 times
Aug 22 11:52:21 standby kernel: cation failed (gfp=0x30/1).
Aug 22 11:52:21 standby kernel: __alloc_pages: 0-order allocation failed (gfp=0x30/1).
Aug 22 11:52:22 standby last message repeated 290 times


-- 

    Tommy Wu
    mailto:tommy@teatime.com.tw
    http://www.teatime.com.tw/~tommy
    ICQ: 22766091
    Mobile Phone: +886 936 909490
    TeaTime BBS +886 2 31515964 24Hrs V.Everything



             reply	other threads:[~2001-08-22  4:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-22  4:47 Tommy Wu [this message]
2001-08-22 19:32 ` Memory Problem in 2.4.9 ? Daniel Phillips
2001-08-22 19:05   ` Marcelo Tosatti
2001-08-23  1:11     ` Daniel Phillips
2001-08-23  0:10       ` Marcelo Tosatti
2001-08-23  2:29         ` Daniel Phillips
2001-08-23  1:19           ` Marcelo Tosatti
  -- strict thread matches above, loose matches on Subject: below --
2001-08-21 13:46 Stephan von Krawczynski
2001-08-21 14:33 ` Daniel Phillips
     [not found]   ` <20010821194140.43b46b10.skraw@ithnet.com>
     [not found]     ` <20010821174918Z16114-32383+718@humbolt.nl.linux.org>
2001-08-21 18:17       ` Stephan von Krawczynski
2001-08-21 19:10         ` Daniel Phillips
2001-08-22  0:04           ` Stephan von Krawczynski
2001-08-22  0:43             ` Daniel Phillips
2001-08-22  0:48               ` Rik van Riel
2001-08-22  1:13                 ` Daniel Phillips
2001-08-22 10:43                   ` Stephan von Krawczynski
     [not found]                   ` <Pine.LNX.4.33.0108220729380.280-100000@mikeg.weiden.de>
2001-08-22 11:01                     ` Stephan von Krawczynski
2001-08-22 17:22                       ` Mike Galbraith
2001-08-22 19:18                         ` Stephan von Krawczynski
2001-08-23  4:57                           ` Mike Galbraith
2001-08-22 11:52           ` Stephan von Krawczynski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010822124255.4DEE.TOMMY@teatime.com.tw \
    --to=tommy@teatime.com.tw \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phillips@bonn-fries.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox