From: Neil Brown <neilb@suse.de>
To: "Yogesh Pahilwan" <Yogesh.Pahilwan@symphonysv.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: Oops in rpciod when building procmail from an NFS client
Date: Thu, 15 Nov 2007 15:04:57 +1100 [thread overview]
Message-ID: <18235.50537.220883.815864@notabene.brown> (raw)
In-Reply-To: message from Yogesh Pahilwan on Wednesday November 14
On Wednesday November 14, Yogesh.Pahilwan@symphonysv.com wrote:
> Hi Folks,
>
>
>
> I am getting following oops while building procmail utility from the NFS
> mounted share when build from the NFS client.
>
> The NFS server oopses in rpciod during the "Benchmarking your system's
> strstr () implementation" step.
>
>
>
> I am using the following configurations for NFS client and server:
>
> NFS client configuration: kernel version - 2.6.11-1.1369_FC4
This is a very old kernel. It is very possible that there is a patch
since then, but it is also possible that it was so long ago that
no-one has a clear memory of it and no-one feels like hunting it down
for you.
I recommend upgrading to a more recent kernel - 2.6.20 at least, and
if the problem persists, report again.
Thanks,
NeilBrown
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-11-15 4:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 6:29 Oops in rpciod when building procmail from an NFS client Yogesh Pahilwan
2007-11-14 8:59 ` Jeff Layton
2007-11-15 4:04 ` Neil Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-13 15:51 Yogesh Pahilwan
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=18235.50537.220883.815864@notabene.brown \
--to=neilb@suse.de \
--cc=Yogesh.Pahilwan@symphonysv.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox