public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Aioanei Rares <krnl.list@gmail.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: 2.6.29.1: Pid: 2831, comm: nfsd Not tainted 2.6.29.1 #4
Date: Tue, 21 Apr 2009 23:00:59 +0300	[thread overview]
Message-ID: <49EE25FB.9050503@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0904211202590.10241@p34.internal.lan>

Justin Piszcz wrote:



> Hello,
>
> This has been happening with 2.6.28.(x) and now 2.6.29.(x), can anyone 
> suggest the possible root cause of this problem, re: the nfsd page 
> allocation
> failures:
>


<snip>

Yes, it happened to me too on a Debian unstable machine with more than 
one kernel, starting with 2.6.28 until now. I have a feeling it's a 
Debian-specific problem rather than a kernel one.

  reply	other threads:[~2009-04-21 20:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-21 16:09 2.6.29.1: Pid: 2831, comm: nfsd Not tainted 2.6.29.1 #4 Justin Piszcz
2009-04-21 20:00 ` Aioanei Rares [this message]
2009-04-22 22:41   ` Jesse Brandeburg
2009-04-22 22:51     ` Justin Piszcz

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=49EE25FB.9050503@gmail.com \
    --to=krnl.list@gmail.com \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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