public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Frank Steiner <fsteiner-mail@bio.ifi.lmu.de>
Cc: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	James Bottomley <James.Bottomley@steeleye.com>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: kblockd/1: page allocation failure in 2.6.9
Date: Fri, 24 Dec 2004 14:20:06 +0100	[thread overview]
Message-ID: <20041224132006.GC2528@suse.de> (raw)
In-Reply-To: <41CAEA62.4060903@bio.ifi.lmu.de>

On Thu, Dec 23 2004, Frank Steiner wrote:
> >Dec 20 13:17:21 turing kernel: kblockd/1: page allocation failure. 
> >order:0, mode:0x21

This looks fishy - this is GFP_ATOMIC | GFP_DMA, where it should only be
GFP_ATOMIC. gdth should not have shost->cmd_pool->gfp_mask ==
GFP_ATOMIC, that looks like a bug in the driver.

Apart from that, the trace looks sane and the SCSI mid layer should
recover from this condition and not cause a hung io subsystem. The only
way I can see this fail is if the scsi host free_list is not filled for
some reason during init, or if the commands allocated from there are
lost or never finished by the hardware.

-- 
Jens Axboe


  reply	other threads:[~2004-12-24 13:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-21  7:39 kblockd/1: page allocation failure in 2.6.9 Frank Steiner
2004-12-23 11:26 ` Frank Steiner
2004-12-23 15:51   ` Denis Vlasenko
2004-12-23 15:55     ` Frank Steiner
2004-12-24 13:20       ` Jens Axboe [this message]
2004-12-24 19:28         ` James Bottomley
2004-12-25 22:49           ` Frank Steiner
2004-12-26 15:46             ` James Bottomley
2004-12-26 22:31               ` Frank Steiner
2005-01-10  9:19                 ` Frank Steiner

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=20041224132006.GC2528@suse.de \
    --to=axboe@suse.de \
    --cc=James.Bottomley@steeleye.com \
    --cc=akpm@osdl.org \
    --cc=fsteiner-mail@bio.ifi.lmu.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /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