Kernel Bug Tracker – Bug 13648
nfsd: page allocation failure
Last modified: 2012-11-20 16:46:57 UTC
Subject : 2.6.30: nfsd: page allocation failure - nfsd or kernel problem? (again with 2.6.30
Submitter : Justin Piszcz <email@example.com>
Date : 2009-06-22 12:08
References : http://lkml.org/lkml/2009/6/22/309
This entry is being used for tracking a regression from 2.6.29. Please don't
close it until the problem is fixed in the mainline.
References : http://marc.info/?l=linux-kernel&m=124748600712853&w=4
Notify-Also : Stephan von Krawczynski <firstname.lastname@example.org>
Notify-Also : David Rientjes <email@example.com>
Notify-Also : Justin Piszcz <firstname.lastname@example.org>
On Monday 27 July 2009, Stephan von Krawczynski wrote:
> On Sun, 26 Jul 2009 22:45:33 +0200 (CEST)
> "Rafael J. Wysocki" <email@example.com> wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.29 and 2.6.30.
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.29 and 2.6.30. Please verify if it still should
> > be listed and let me know (either way).
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13648
> > Subject : nfsd: page allocation failure
> > Submitter : Justin Piszcz <firstname.lastname@example.org>
> > Date : 2009-06-22 12:08 (35 days old)
> > References : http://lkml.org/lkml/2009/6/22/309
> > http://marc.info/?l=linux-kernel&m=124748600712853&w=4
> This is no regression between 2.6.29 and 2.6.30.
> In fact we could reproduce the problem with kernel versions:
> 220.127.116.11 < X <= 18.104.22.168
> (Meaning 22.214.171.124 is the last one _not_ showing the problem).
Moving to the list of regressions from 2.6.27.
I see a lot of these with 126.96.36.199-28.rc2.fc11.i686.PAE and e1000.
Did this issue get resolved somehow?
There is some discussion about shutting the warning off, but I couldn't quite follow.... ( http://patchwork.kernel.org/patch/30960/ )
I'm still seeing with 188.8.131.52-149.fc13.i686.
Ok, thanks for the feedback.