From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail203.messagelabs.com (mail203.messagelabs.com [216.82.254.243]) by kanga.kvack.org (Postfix) with ESMTP id 8597F6B01FF for ; Mon, 26 Apr 2010 08:15:21 -0400 (EDT) Subject: Re: [Bugme-new] [Bug 15709] New: swapper page allocation failure From: Trond Myklebust In-Reply-To: <20100425204916.GA12686@redhat.com> References: <4BC43097.3060000@tauceti.net> <4BCC52B9.8070200@tauceti.net> <20100419131718.GB16918@redhat.com> <20100421094249.GC30855@redhat.com> <20100422100304.GC30532@redhat.com> <4BD12F9C.30802@tauceti.net> <20100425091759.GA9993@redhat.com> <4BD4A917.70702@tauceti.net> <20100425204916.GA12686@redhat.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Date: Mon, 26 Apr 2010 08:15:54 -0400 Message-ID: <1272284154.4252.34.camel@localhost.localdomain> Mime-Version: 1.0 Sender: owner-linux-mm@kvack.org To: "Michael S. Tsirkin" Cc: Robert Wimmer , Avi Kivity , Andrew Morton , linux-mm@kvack.org, bugzilla-daemon@bugzilla.kernel.org, Rusty Russell , Mel Gorman , linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org List-ID: On Sun, 2010-04-25 at 23:49 +0300, Michael S. Tsirkin wrote:=20 > So, it's an NFS-related regression, which is consistent with the bisect > results. I guess someone who knows about NFS will have to look at it... > BTW, you probably want to label the bug as regression. >=20 > On Sun, Apr 25, 2010 at 10:41:59PM +0200, Robert Wimmer wrote: > > I've added CONFIG_KALLSYMS and CONFIG_KALLSYMS_ALL > > to my .config. I've uploaded the dmesg output. Maybe it > > helps a little bit: > >=20 > > https://bugzilla.kernel.org/attachment.cgi?id=3D26138 > >=20 > > - Robert > >=20 That last trace is just saying that the NFSv4 reboot recovery code is crashing (which is hardly surprising if the memory management is hosed). The initial bisection makes little sense to me: it is basically blaming a page allocation problem on a change to the NFSv4 mount code. The only way I can see that possibly happen is if you are hitting a stack overflow. So 2 questions: - Are you able to reproduce the bug when using NFSv3 instead? - Have you tried running with stack tracing enabled? Cheers Trond -- 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