public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Douglas Gilbert <dougg@torque.net>
To: Marcelo Tosatti <marcelo@conectiva.com.br>, linux-kernel@vger.kernel.org
Subject: Re: __alloc_pages: 3-order allocation failed.
Date: Sun, 12 Aug 2001 22:20:23 -0400	[thread overview]
Message-ID: <3B773967.4A3B426A@torque.net> (raw)

Marcelo wrote:
> > On Sun, 12 Aug 2001, André Dahlqvist wrote:
> > With recent kernel, 2.4.7 and 2.4.8 my syslog file has been filled with
> > these messages:
> > 
> > Aug 12 02:08:58 sledgehammer kernel: __alloc_pages: 3-order allocation failed.
> > Aug 12 02:08:58 sledgehammer kernel: __alloc_pages: 2-order allocation failed.
> > Aug 12 02:08:58 sledgehammer kernel: __alloc_pages: 1-order allocation failed.
> > Aug 12 02:08:58 sledgehammer kernel: __alloc_pages: 3-order allocation failed.
> > 
> > I have not yet found a pattern for when it happens but it doesn't seam to
> > affect my system all that much. Let me know if you want further info or if
> > this is a known thing.
> 
> Are you using SCSI?

Marcelo,
That looks just like the sg driver trying to build a
scatter gather list, first it tries 32 KB, then 16 KB
then 8 KB and final gets PAGE_SIZE. This is _not_ an
error (it just leads to more elements in the scatter
gather list).

Any chance that printk() in __alloc_pages() can be removed?

Doug Gilbert



             reply	other threads:[~2001-08-13  3:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-13  2:20 Douglas Gilbert [this message]
2001-08-13  2:04 ` __alloc_pages: 3-order allocation failed Marcelo Tosatti
  -- strict thread matches above, loose matches on Subject: below --
2001-08-12  0:58 André Dahlqvist
2001-08-13  0:32 ` Marcelo Tosatti
2001-08-13  2:05   ` André Dahlqvist

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=3B773967.4A3B426A@torque.net \
    --to=dougg@torque.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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