Bug 438087 - unexplained kernel segfault and knot trap divide errors
Summary: unexplained kernel segfault and knot trap divide errors
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel
Version: 4.5
Hardware: x86_64
OS: Linux
low
high
Target Milestone: rc
: ---
Assignee: Red Hat Kernel Manager
QA Contact: Martin Jenner
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-03-18 22:43 UTC by Markos Gogoulos
Modified: 2012-06-20 13:33 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-20 13:33:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Markos Gogoulos 2008-03-18 22:43:50 UTC
Description of problem:

in our Scientific Linux cluster (SL 4.5 64bit) we have received the following
two errors:

wn014: Mar 12 09:09:20 wn014 kernel: knot[24574] trap divide error rip:405894
rsp:7fbfffe520 error:0

wn057: Feb 27 04:31:44 wn057 kernel: fs[4851]: segfault at 00000000ed410c22 rip
00000033ed3707b0 rsp 0000007fbfffb2a8 error 4

Errors are repeated many times (each 4-5 seconds) and appear every few days on
most of the nodes. 

Version-Release number of selected component (if applicable):


How reproducible:

All nodes have 2.6.9-67.0.4.ELsmp x86_64 kernel and run a small set of ordinary
services, plus a gpfs client software to mount a gpfs filesystem. Could the last
one be creating the issues?
Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Have you experienced this before? Could you point us at how we can source the
problem or increase the level of debugging, so we can provide more valuable
information?

Comment 1 Jiri Pallich 2012-06-20 13:33:27 UTC
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.


Note You need to log in before you can comment on or make changes to this bug.