From: Stan Hoeppner <stan@hardwarefreak•com>
To: Pekka Enberg <penberg@kernel•org>
Cc: Christoph Lameter <cl@linux•com>,
Mikael Abrahamsson <swmike@swm•pp.se>,
Linux Kernel List <linux-kernel@vger•kernel.org>,
linux-mm@kvack•org, Mel Gorman <mel@csn•ul.ie>,
Linux Netdev List <netdev@vger•kernel.org>
Subject: Re: 2.6.34.1 page allocation failure
Date: Tue, 24 Aug 2010 14:08:35 -0500 [thread overview]
Message-ID: <4C7418B3.5060103@hardwarefreak.com> (raw)
In-Reply-To: <4C74097A.5020504@kernel.org>
Pekka Enberg put forth on 8/24/2010 1:03 PM:
> It looks to me as if tcp_create_openreq_child() is able to cope with the
> situation so the warning could be harmless. If that's the case, we
> should probably stick a __GFP_NOWARN there.
If it would be helpful, here's a complete copy of dmesg:
http://www.hardwarefreak.com/2.6.34.1-dmesg-oopses.txt
Something I forgot to mention earlier is that every now and then I
unmount swap and drop caches to clear things out a bit. Not sure if
that may be relevant, but since it has to do with memory allocation I
thought I'd mention it.
--
Stan
--
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:[~2010-08-24 19:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4C70BFF3.8030507@hardwarefreak.com>
[not found] ` <alpine.DEB.1.10.1008220842400.8562@uplift.swm.pp.se>
[not found] ` <AANLkTin48SJ58HvFqjrOnQBMqLcbECtqXokweV00dNgv@mail.gmail.com>
[not found] ` <alpine.DEB.2.00.1008221734410.21916@router.home>
[not found] ` <4C724141.8060000@kernel.org>
[not found] ` <4C72F7C6.3020109@hardwarefreak.com>
2010-08-24 18:03 ` 2.6.34.1 page allocation failure Pekka Enberg
2010-08-24 19:08 ` Stan Hoeppner [this message]
2010-08-24 19:21 ` Mikael Abrahamsson
2010-08-29 10:49 ` Pekka Enberg
2010-08-29 12:38 ` Mikael Abrahamsson
2010-08-29 13:17 ` Pekka Enberg
2010-08-29 15:37 ` Mikael Abrahamsson
2010-08-31 20:28 ` Mikael Abrahamsson
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=4C7418B3.5060103@hardwarefreak.com \
--to=stan@hardwarefreak$(echo .)com \
--cc=cl@linux$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mm@kvack$(echo .)org \
--cc=mel@csn$(echo .)ul.ie \
--cc=netdev@vger$(echo .)kernel.org \
--cc=penberg@kernel$(echo .)org \
--cc=swmike@swm$(echo .)pp.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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