All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jeff L. Smith" <jeff@atheros.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: nfs@lists.sourceforge.net
Subject: Re: Vaguely NFS related problem
Date: Thu, 12 Dec 2002 09:09:19 -0800	[thread overview]
Message-ID: <3DF8C2BF.8050109@atheros.com> (raw)
In-Reply-To: 15863.64480.756681.957850@notabene.cse.unsw.edu.au

You are correct.  The only patch I applied was Trond's 
linux-2.4.18-NFS_ALL.dif and that is where the check is.  The actual 
patch was linux-2.4.18-svc_tcp.dif.  I'm not doing NFS-over-TPC, but 
this seems to be biting me anyway.

I plan to upgrade to 2.4.20 as soon as I can take the fileservers down 
long enough, but that will be a few weeks.  But then that begs the 
question, should I apply Trond's 2.4.20 patches?

Thanks,
Jeff

Neil Brown wrote:
> On Wednesday December 11, jeff@atheros.com wrote:
> 
>>I'm running a kernel I built from kernel.org source.  I found the 
>>message in linux-2.4.18/net/sunrpc/svcsock.c.
>>
>>
>>printk (KERN_WARNING "RPC: Unable to allocate resbuf from cache!\n");
> 
> 
> I think you should check again.  I did and I still cannot find that
> message:
> 
> % bzcat linux-2.4.18.tar.bz2 | grep 'Unable to allocate resbuf from cache'
> %
> 
> Are you sure they were *unpatched* kernel.org sources?
> 
> I suggest you unroll 2.4.20 and try that.
> 
> NeilBrown


-- 
Jeff Smith                                  Atheros Communications, Inc.
Hardware Manager                            529 Almanor Avenue
(408) 773-5257                              Sunnyvale, CA  94086



-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2002-12-12 17:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-12  1:47 Vaguely NFS related problem Jeff L. Smith
2002-12-12  2:12 ` Neil Brown
2002-12-12  2:37   ` Jeff L. Smith
2002-12-12  3:00     ` Neil Brown
2002-12-12 17:09       ` Jeff L. Smith [this message]
2002-12-13 14:07         ` Trond Myklebust
  -- strict thread matches above, loose matches on Subject: below --
2002-12-12  2:41 Jeff L. Smith

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=3DF8C2BF.8050109@atheros.com \
    --to=jeff@atheros.com \
    --cc=neilb@cse.unsw.edu.au \
    --cc=nfs@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.