All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Ingo Freund <Ingo.Freund@e-dict.net>
Cc: linux-kernel@vger.kernel.org, achim@vortex.de
Subject: Re: memory allocation error messages in system log
Date: Thu, 16 Sep 2004 18:14:08 -0300	[thread overview]
Message-ID: <20040916211408.GE12022@logos.cnet> (raw)
In-Reply-To: <NEBBILBHKLDLOMLDGKGNEEKDCIAA.Ingo.Freund@e-dict.net>

On Thu, Sep 16, 2004 at 02:48:40PM +0200, Ingo Freund wrote:
> Hello,
> 
> I hope you guys can help, I cannot use any kernel 2.4 >23 without
> the here described problem.
> 
> [1.] One line summary of the problem:
> strange error messages concerning memory allocation
> 
> searching teh web for solutions to my problem I have already found
> a thread in a mailing list but no solution was mentioned, also the
> guys who talked about the error didn't answer to my direct mail.
> 
> [2.] Full description of the problem/report:
> The machine is a database server without any other service except sshd
> running. I do some tests on the ICP-Vortex GDT controller every 2 minutes.
> by using
> # cat /proc/scsi/gdt/2
> but the output of cat stops without beeing completed.
> 
> This is what I see in the syslog file every time when I use the cat
> command (the messages beginn after 3 days uptime):
> --> /var/log/messages
> kernel: __alloc_pages: 0-order allocation failed (gfp=0x21/0)

Ingo,

I've seen another report like this one - I'm convinced there
is something odd with the gdth proc handling code.

Can you "echo 1 > /proc/sys/vm/vm_gfp_debug" and 
rerun the "cat /proc/scsi/gdt/2" please?

  reply	other threads:[~2004-09-16 22:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-16 12:48 memory allocation error messages in system log Ingo Freund
2004-09-16 21:14 ` Marcelo Tosatti [this message]
2004-09-18  1:04   ` Marcelo Tosatti
2004-09-18  4:52     ` Willy Tarreau

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=20040916211408.GE12022@logos.cnet \
    --to=marcelo.tosatti@cyclades.com \
    --cc=Ingo.Freund@e-dict.net \
    --cc=achim@vortex.de \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.