Description of problem:
When accessing an NFS mount directory, process hangs, and message is
logged in messages file
init: PANIC: segmentation violation at 0x81889288! sleeping for 30
kernel: RPC: buffer allocation failed for task ed66bca8
After reboot the system, everything goes normal for a few days, and
the problem occurs again.
Version-Release number of selected component (if applicable):
Redhat Linux WS release 3 (Taroon Update 2)
Steps to Reproduce:
1. reboot the system, everyhting is good
2. wait for a few days (2 days)
3. run "ls /mnt/nfs_m"
ls not hang
Hello, George. Could you please provide more detail on how to
reproduce this problem? Is waiting for a few days (step 2) a
critical part of the scenario? If so, what was happening on
both the client and server machines during the 2-day window?
It would be far more useful to us if you could provide a
faster way to reproduce this problem.
In the meantime, I'm assigning this bug to our NFS/RPC maintainter.
Looks waiting for a few days is important. It seems time matters. The
system was sitting idle most of the time before problem occurred.
The NFS sever machine was serving about 50 clients and all other
clients had no problem.
I don't know how to reproduce the problem sooner.
This looks to me like VM issue.... Reassigning...
Steve, the "init: PANIC: segmentation violation" message doesn't
originate from the kernel. My guess is that this was a symptom
of the RPC buffer allocation failure. Plus, since the trigger
for the problem is an NFS access, it's less likely to be related
to any VM issue.
By the way, this looks like a possible dup of bug #118839, which
is assigned to you.
For now, I'm bouncing this back to you but will add Larry to the
*** This bug has been marked as a duplicate of 118839 ***
A fix for this problem has just been committed to the RHEL3 U4
patch pool this evening (in kernel version 2.4.21-20.7.EL).
An errata has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.