Subject : 2.6.38-rc5: nfsd: page allocation failure. spinlock trylock failure on UP
Submitter : Alexander Beregalov <firstname.lastname@example.org>
Date : 2011-02-21 20:33
Message-ID : AANLkTi=14N_c_B7mLY0H8Dt8pte6C0mjFnVuC37e44Hs@mail.gmail.com
References : http://marc.info/?l=linux-netdev&m=129832042402668&w=2
This entry is being used for tracking a regression from 2.6.37. Please don't
close it until the problem is fixed in the mainline.
Looks like a potential networking issue to me, but reassigning to Bruce
in case it really is a NFS server bug.
Definitely not something I've seen, and I can't think of any nfsd change that might have caused it.
On Sunday, April 17, 2011, Alexander Beregalov wrote:
> On 17 April 2011 17:52, 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.37 and 2.6.38.
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.37 and 2.6.38. Please verify if it still should
> > be listed and let the tracking team know (either way).
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=29852
> > Subject : 2.6.38-rc5: nfsd: page allocation failure. spinlock
> trylock failure on UP
> > Submitter : Alexander Beregalov <firstname.lastname@example.org>
> > Date : 2011-02-21 20:33 (56 days old)
> I do not see the problem since that time.