From: Peter Zijlstra <peterz@infradead.org>
To: Alex Samad <alex@samad.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: page swap allocation error/failure in 2.6.25
Date: Fri, 25 Jul 2008 09:40:01 +0200 [thread overview]
Message-ID: <1216971601.7257.345.camel@twins> (raw)
In-Reply-To: <20080725072015.GA17688@samad.com.au>
On Fri, 2008-07-25 at 17:20 +1000, Alex Samad wrote:
> Hi
>
> I reported this earlier (http://lkml.org/lkml/2008/7/13/41) which I had
> attributed to miss match mtu and route information.
>
> But I have started to see the errors again.
>
>
> Jul 25 13:07:07 hufpuf kernel: [269282.912693] swapper: page allocation
> failure. order:2, mode:0x20
> Jul 25 13:07:07 hufpuf kernel: [269282.912700] Pid: 0, comm: swapper
> Tainted: GF 2.6.25-2-amd64 #1
> Jul 25 13:07:07 hufpuf kernel: [269282.912703]
> Jul 25 13:07:07 hufpuf kernel: [269282.912703] Call Trace:
> Jul 25 13:07:07 hufpuf kernel: [269282.912705] <IRQ>
> [<ffffffff8027709a>] __alloc_pages+0x2f8/0x312
> Jul 25 13:07:07 hufpuf kernel: [269282.912750] [<ffffffff80294c63>]
> kmem_getpages+0xc5/0x193
> Jul 25 13:07:07 hufpuf kernel: [269282.912757] [<ffffffff8029529d>]
> fallback_alloc+0x147/0x1c0
> Jul 25 13:07:07 hufpuf kernel: [269282.912769] [<ffffffff80294ed8>]
> kmem_cache_alloc_node+0x105/0x138
> Jul 25 13:07:07 hufpuf kernel: [269282.912777] [<ffffffff803ac4ae>]
> __alloc_skb+0x64/0x12d
Its harmless if it happens sporadically.
Atomic order 2 allocations are just bound to go wrong under pressure.
next prev parent reply other threads:[~2008-07-25 7:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 7:20 page swap allocation error/failure in 2.6.25 Alex Samad
2008-07-25 7:40 ` Peter Zijlstra [this message]
2008-07-27 6:07 ` Alex Samad
2008-07-28 10:04 ` Peter Zijlstra
2008-07-28 10:04 ` Peter Zijlstra
2008-07-29 0:06 ` Alex Samad
2008-07-29 9:14 ` Mel Gorman
2008-07-29 9:14 ` Mel Gorman
2008-07-29 9:58 ` Alex Samad
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=1216971601.7257.345.camel@twins \
--to=peterz@infradead.org \
--cc=alex@samad.com.au \
--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.