Bug 204771 - Bad EIP Value
Summary: Bad EIP Value
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel   
(Show other bugs)
Version: 3.0
Hardware: i386 Linux
medium
urgent
Target Milestone: ---
Assignee: Red Hat Kernel Manager
QA Contact: Brian Brock
URL:
Whiteboard:
Keywords:
: 204773 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-08-31 14:28 UTC by Sybille B.
Modified: 2008-05-01 22:38 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-05-01 22:38:15 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)
screen shot (312.00 KB, application/msword)
2006-08-31 19:13 UTC, Sybille B.
no flags Details

Description Sybille B. 2006-08-31 14:28:51 UTC
Description of problem:
Server Crash with following error message on screen:
Code: Bad EIP Value.
Kernel Panic: Fatal Exception

Version-Release number of selected component (if applicable):
Linux 3AS Update 4
2.4.21-27.ELhugemem

How reproducible:
Systems crashed everyday at least one time for the past three days.

Steps to Reproduce:
1.Copying big files (30GB) from one local partition or nfs mount.
2.
3.
  
Additional info:
Refer to screen shots attached from the same server for error messages.

Is this problem same as the following?
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=150334

What suggestions to you have to solve this recurrent problem?

Comment 1 Sybille B. 2006-08-31 19:13:21 UTC
Created attachment 135321 [details]
screen shot

Comment 2 Prarit Bhargava 2007-09-13 18:42:30 UTC
*** Bug 204773 has been marked as a duplicate of this bug. ***

Comment 3 Don Howard 2008-05-01 22:38:15 UTC
A number of bugs have corrected since the 2.4.21-27 era.  If this can be
reproduced on a recent kernel (2.4.21-56 or newer) please open a new bug.


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