From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail137.messagelabs.com (mail137.messagelabs.com [216.82.249.19]) by kanga.kvack.org (Postfix) with SMTP id A1F206B01F0 for ; Tue, 24 Aug 2010 15:06:29 -0400 (EDT) Message-ID: <4C7418B3.5060103@hardwarefreak.com> Date: Tue, 24 Aug 2010 14:08:35 -0500 From: Stan Hoeppner MIME-Version: 1.0 Subject: Re: 2.6.34.1 page allocation failure References: <4C70BFF3.8030507@hardwarefreak.com> <4C724141.8060000@kernel.org> <4C72F7C6.3020109@hardwarefreak.com> <4C74097A.5020504@kernel.org> In-Reply-To: <4C74097A.5020504@kernel.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org To: Pekka Enberg Cc: Christoph Lameter , Mikael Abrahamsson , Linux Kernel List , linux-mm@kvack.org, Mel Gorman , Linux Netdev List List-ID: 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: email@kvack.org