Bug 127830 - init: PANIC: segmentation violation
Summary: init: PANIC: segmentation violation
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel (Show other bugs)
(Show other bugs)
Version: 3.0
Hardware: i386 Linux
medium
high
Target Milestone: ---
Assignee: Steve Dickson
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-07-14 14:04 UTC by George
Modified: 2007-11-30 22:07 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-12-20 20:55:40 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2004:550 normal SHIPPED_LIVE Updated kernel packages available for Red Hat Enterprise Linux 3 Update 4 2004-12-20 05:00:00 UTC

Description George 2004-07-14 14:04:05 UTC 
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
seconds.
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):

kernel-smp-2.4.21-15.0.3.EL
Redhat Linux WS release 3 (Taroon Update 2)

How reproducible:
Always

Steps to Reproduce:
1. reboot the system, everyhting is good
2. wait for a few days (2 days)
3. run "ls /mnt/nfs_m"


Expected results:
ls not hang

Additional info:
Comment 1 Ernie Petrides 2004-07-14 18:12:10 UTC 
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.
Comment 2 George 2004-07-14 20:00:31 UTC 
Hi Ernie,

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.
Thanks.
Comment 3 Steve Dickson 2004-07-16 01:08:56 UTC 
This looks to me like VM issue.... Reassigning...
Comment 4 Ernie Petrides 2004-07-16 21:06:22 UTC 
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
cc: list.
Comment 5 Steve Dickson 2004-07-30 13:23:12 UTC 

*** This bug has been marked as a duplicate of 118839 ***
Comment 6 Ernie Petrides 2004-09-18 06:07:24 UTC 
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).
Comment 7 John Flanagan 2004-12-20 20:55:40 UTC 
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.

http://rhn.redhat.com/errata/RHBA-2004-550.html
Note You need to log in before you can comment on or make changes to this bug.