From: Andrew Morton <akpm@osdl.org>
To: Oliver Kiddle <okiddle@yahoo.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: page allocation failure
Date: Thu, 22 Jan 2004 01:59:05 -0800 [thread overview]
Message-ID: <20040122015905.7c16b86a.akpm@osdl.org> (raw)
In-Reply-To: <11370.1074763788@gmcs3.local>
Oliver Kiddle <okiddle@yahoo.co.uk> wrote:
>
> st0: Block limits 1 - 16777215 bytes.
> xfsdump: page allocation failure. order:9, mode:0xd0
> Call Trace:
> [<c0132d18>] __alloc_pages+0x2db/0x319
> [<c02a5dc9>] enlarge_buffer+0xcf/0x182
> [<c02a6cd9>] st_map_user_pages+0x37/0x88
> [<c02a2909>] setup_buffering+0xf3/0x127
> [<c02a3690>] st_read+0xe0/0x3d1
> [<c0147625>] vfs_read+0xb0/0x119
> [<c01478a0>] sys_read+0x42/0x63
> [<c0108ab7>] syscall_call+0x7/0xb
This one's actually somewhat OK. The tape driver is simply trying to
allocate a huge buffer and is falling back if it fails.
This will shut up the debugging code:
--- 25/drivers/scsi/osst.c~osst-warning-fix 2004-01-22 01:57:35.000000000 -0800
+++ 25-akpm/drivers/scsi/osst.c 2004-01-22 01:57:59.000000000 -0800
@@ -5106,6 +5106,8 @@ static int enlarge_buffer(OSST_buffer *S
if (need_dma)
priority |= GFP_DMA;
+ priority |= __GFP_NOWARN;
+
/* Try to allocate the first segment up to OS_DATA_SIZE and the others
big enough to reach the goal (code assumes no segments in place) */
for (b_size = OS_DATA_SIZE, order = OSST_FIRST_ORDER; b_size >= PAGE_SIZE; order--, b_size /= 2) {
_
next prev parent reply other threads:[~2004-01-22 9:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 11:36 Oliver Kiddle
2004-01-19 14:54 ` Mike Fedyk
2004-01-19 17:29 ` Oliver Kiddle
2004-01-19 18:12 ` Mike Fedyk
2004-01-20 3:38 ` Andrew Morton
2004-01-20 6:00 ` Nathan Scott
2004-01-20 17:08 ` Oliver Kiddle
2004-01-20 18:35 ` Mike Fedyk
2004-01-22 9:29 ` Oliver Kiddle
2004-01-22 9:59 ` Andrew Morton [this message]
2004-08-24 20:05 Dominik Karall
2004-08-24 20:05 ` Andrew Morton
2004-08-24 22:57 ` David S. Miller
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=20040122015905.7c16b86a.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=okiddle@yahoo.co.uk \
/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
Powered by JetHome