From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: page allocation failure
Date: Thu, 22 Jan 2004 10:29:48 +0100 [thread overview]
Message-ID: <11370.1074763788@gmcs3.local> (raw)
In-Reply-To: <20040120183556.GE23765@srv-lnx2600.matchmail.com>
Mike Fedyk wrote:
> On Tue, Jan 20, 2004 at 06:08:34PM +0100, Oliver Kiddle wrote:
> > the message about the tape device. As suggested by Mike Fedyk, I had
> > the nmi_watchdog stuff enabled. Didn't see any output from it though.
> > Would that have displayed its output to the console?
>
> It should have. Run cat /proc/interrupts and again afew seconds later, does
> the NMI: number change?
Yes, the number changes. Still haven't seen any output from it though.
> There should be some lines above this in your log...
Only the trace for other processes. Any initial part was lost, probably
because the task list overflowed the dmesg buffer. I didn't see anything
on the console though.
I got a few page allocation errors yesterday. As they now include
dump_stack() output, I have attached them below. This time, the system
kept going for a few minutes after these error messages. Again, when it
locked up, killing all processes with the sysrq key got things temporarily
back. I have the full dmesg output if anyone wants.
Oliver
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
xfsdump: page allocation failure. order:8, 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
xfsdump: page allocation failure. order:7, 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
st0: Incorrect block size.
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
[<c02a2b86>] st_write+0x20c/0x7e7
[<c0115ecb>] do_page_fault+0x120/0x501
[<c02a297a>] st_write+0x0/0x7e7
[<c01477f5>] vfs_write+0xb0/0x119
[<c0147903>] sys_write+0x42/0x63
[<c0108ab7>] syscall_call+0x7/0xb
xfsdump: page allocation failure. order:8, 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
[<c02a2b86>] st_write+0x20c/0x7e7
[<c0115ecb>] do_page_fault+0x120/0x501
[<c02a297a>] st_write+0x0/0x7e7
[<c01477f5>] vfs_write+0xb0/0x119
[<c0147903>] sys_write+0x42/0x63
[<c0108ab7>] syscall_call+0x7/0xb
xfsdump: page allocation failure. order:7, 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
[<c02a2b86>] st_write+0x20c/0x7e7
[<c0115ecb>] do_page_fault+0x120/0x501
[<c02a297a>] st_write+0x0/0x7e7
[<c01477f5>] vfs_write+0xb0/0x119
[<c0147903>] sys_write+0x42/0x63
[<c0108ab7>] syscall_call+0x7/0xb
next prev parent reply other threads:[~2004-01-22 9:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 11:36 page allocation failure 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 [this message]
2004-01-22 9:59 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2004-08-24 20:05 Dominik Karall
2004-08-24 20:05 ` Andrew Morton
2004-08-24 22:57 ` David S. Miller
2004-11-11 10:11 sai srinivas dharanikota
2004-11-12 8:32 ` Keir Fraser
2008-06-14 2:25 Denys Fedoryshchenko
2008-06-14 6:58 ` Evgeniy Polyakov
2008-06-14 21:02 ` Denys Fedoryshchenko
2008-06-14 21:36 ` Ben Hutchings
2008-06-15 6:04 ` Evgeniy Polyakov
2010-04-06 12:15 kvm
2010-04-06 10:59 ` Thomas Mueller
2010-04-06 13:46 ` kvm
2012-07-30 13:25 Shawn Joo
2012-07-30 14:13 ` Michal Hocko
2012-07-31 5:32 ` Shawn Joo
2012-07-31 13:52 ` Michal Hocko
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=11370.1074763788@gmcs3.local \
--to=okiddle@yahoo.co.uk \
--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.