Bug 78547 - Internal Error: Illegal Instruction & Segmentation Fault
Internal Error: Illegal Instruction & Segmentation Fault
Status: CLOSED WORKSFORME
Product: Red Hat Linux
Classification: Retired
Component: gcc (Show other bugs)
7.3
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jakub Jelinek
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-11-25 11:32 EST by Nathanael Noblet
Modified: 2007-04-18 12:48 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-11-25 11:32:11 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Nathanael Noblet 2002-11-25 11:32:04 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
When trying to compile any kernel version. The compiler crashes at random places
with "Internal Error: Illegal Instruction" and sometimes "Internal Error:
Segmentation Fault". The machine is a K6-2 350 with 64MB of RAM. I had RH 7.3
installed and all updates made. Various kernel versions trying to compile all
generate the same thing. The error does not happen at the same place, and after
one error I can enter "make bzImage" again and it will continue past the
previous error, continue on for awhile and crash again. Eventually after a
number of errors, it will complete the compile.

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


How reproducible:
Always

Steps to Reproduce:
1.Get kernel sources
2.make menuconfig or make xconfig
3.make bzImage
	

Actual Results:  Randomly crashes at various stages in the compile.

Expected Results:  A clean compile

Additional info:
Comment 1 Jakub Jelinek 2002-11-25 11:34:55 EST
This is typical symptom of bad hardware.
Check your memory with memtest86, check other components.

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