From: Nathan Scott <nathans@sgi.com>
To: linux-kernel@vger.kernel.org
Subject: ST alloc failures
Date: Fri, 2 Apr 2004 15:13:55 +1000 [thread overview]
Message-ID: <20040402051355.GA1604@frodo> (raw)
Hi all,
I'm seeing a bunch of large allocation attempts failing from
the SCSI tape driver when doing dumps and restores ... (this
is with a stock 2.6.4 kernel).
xfsdump: page allocation failure. order:8, mode:0xd0
Call Trace:
[<c013982b>] __alloc_pages+0x33b/0x3d0
[<c03805ac>] enlarge_buffer+0xdc/0x1b0
[<c03819a3>] st_map_user_pages+0x33/0x90
[<c037cf24>] setup_buffering+0xb4/0x160
[<c037dd19>] st_read+0x109/0x450
[<c01173e3>] kernel_map_pages+0x33/0x68
[<c015464f>] vfs_read+0xaf/0x120
[<c0153c48>] sys_open+0x78/0x90
[<c01548df>] sys_read+0x3f/0x60
[<c01094e1>] sysenter_past_esp+0x52/0x71
xfsdump: page allocation failure. order:7, mode:0xd0
Call Trace:
[<c013982b>] __alloc_pages+0x33b/0x3d0
[<c03805ac>] enlarge_buffer+0xdc/0x1b0
[<c03819a3>] st_map_user_pages+0x33/0x90
[<c037cf24>] setup_buffering+0xb4/0x160
[<c037dd19>] st_read+0x109/0x450
[<c01173e3>] kernel_map_pages+0x33/0x68
[<c015464f>] vfs_read+0xaf/0x120
[<c0153c48>] sys_open+0x78/0x90
[<c01548df>] sys_read+0x3f/0x60
[<c01094e1>] sysenter_past_esp+0x52/0x71
xfsrestore: page allocation failure. order:8, mode:0xd0
Call Trace:
[<c013982b>] __alloc_pages+0x33b/0x3d0
[<c03805ac>] enlarge_buffer+0xdc/0x1b0
[<c03819a3>] st_map_user_pages+0x33/0x90
[<c037cf24>] setup_buffering+0xb4/0x160
[<c037dd19>] st_read+0x109/0x450
[<c01173e3>] kernel_map_pages+0x33/0x68
[<c015464f>] vfs_read+0xaf/0x120
[<c0153c48>] sys_open+0x78/0x90
[<c01548df>] sys_read+0x3f/0x60
[<c01094e1>] sysenter_past_esp+0x52/0x71
xfsrestore: page allocation failure. order:7, mode:0xd0
Call Trace:
[<c013982b>] __alloc_pages+0x33b/0x3d0
[<c03805ac>] enlarge_buffer+0xdc/0x1b0
[<c03819a3>] st_map_user_pages+0x33/0x90
[<c037cf24>] setup_buffering+0xb4/0x160
[<c037dd19>] st_read+0x109/0x450
[<c01173e3>] kernel_map_pages+0x33/0x68
[<c015464f>] vfs_read+0xaf/0x120
[<c0153c48>] sys_open+0x78/0x90
[<c01548df>] sys_read+0x3f/0x60
[<c01094e1>] sysenter_past_esp+0x52/0x71
cheers.
--
Nathan
next reply other threads:[~2004-04-02 4:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-02 5:13 Nathan Scott [this message]
2004-04-02 6:32 ` ST alloc failures Christoph Hellwig
2004-04-03 7:19 ` Kai Makisara
2004-04-06 8:48 ` Nathan Scott
2004-04-06 19:09 ` Kai Makisara
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=20040402051355.GA1604@frodo \
--to=nathans@sgi.com \
--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.