From: John Hughes <john@calva.com>
To: Andrew Morton <akpm@linux-foundation.org>, linux-mm@kvack.org
Cc: bugzilla-daemon@bugzilla.kernel.org,
Mel Gorman <mgorman@techsingularity.net>
Subject: Re: [Bug 107111] New: page allocation failure but there seem to be free pages
Date: Wed, 04 Nov 2015 11:10:18 +0100 [thread overview]
Message-ID: <5639D98A.80308@calva.com> (raw)
In-Reply-To: <20151103141603.261893b44e0cd6e704921fb6@linux-foundation.org>
On 03/11/15 23:16, Andrew Morton wrote:
> (switched to email. Please respond via emailed reply-to-all, not via the
> bugzilla web interface).
OK.
>
> On Tue, 03 Nov 2015 16:21:06 +0000 bugzilla-daemon@bugzilla.kernel.org wrote:
>
>> https://bugzilla.kernel.org/show_bug.cgi?id=107111
>>
>> Bug ID: 107111
>> Summary: page allocation failure but there seem to be free
>> pages
>> Product: Memory Management
>> Version: 2.5
>> Kernel Version: 4.2.3
>> Hardware: IA-64
>> 18
> Note: IA64. It isn't tested much and perhaps this triggered an oddity.
Sorry, user error, it's x86-64, not IA64, a KVM guest running on a
"Intel(R) Xeon(R) CPU 3050".
> The kernel could and should have satisfied this order-1 GFP_ATOMIC
> IRQ-context allocation from the DMA zone. But it did not do so. Bug.
Looking back in my kern.logs I confirm that I've only seen this on
kernel 4.2.3, never on the 3.18.19 I was running up to 16/10/2015. It
happens up to 15 times a day, and, so far, hasn't happened since I upped
/proc/sys/vm/min_free_kbytes to 8192.
--
John Hughes.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-11-04 10:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-107111-27@https.bugzilla.kernel.org/>
2015-11-03 22:16 ` [Bug 107111] New: page allocation failure but there seem to be free pages Andrew Morton
2015-11-04 10:10 ` John Hughes [this message]
2015-11-04 10:20 ` 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=5639D98A.80308@calva.com \
--to=john@calva.com \
--cc=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
/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.