Bug 62664 - AMD K6-II, 2.4.9-31, compile segmentation fault
AMD K6-II, 2.4.9-31, compile segmentation fault
Product: Red Hat Linux
Classification: Retired
Component: gcc (Show other bugs)
i586 Linux
medium Severity medium
: ---
: ---
Assigned To: Jakub Jelinek
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2002-04-03 17:48 EST by Need Real Name
Modified: 2007-04-18 12:41 EDT (History)
1 user (show)

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

Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2002-04-03 17:48:55 EST
Description of Problem:

K6-II, 2.4.9-31, make bzImage fails at random locations when working 
in the 'drivers' directory.  Failure always occurs in the 'drivers'
directory but at differing sub-directories.For eample:

serial.c: In function `probe_serial_pci':
serial.c:4919: Internal error: Segmentation fault.
Please submit a full bug report.
See <URL:http://bugzilla.redhat.com/bugzilla/> for instructions.
make[3]: *** [serial.o] Error 2
make[3]: Leaving directory `/usr/src/linux-2.4.9-31/drivers/char'

This despite having replaced rpms.  Did rpm -Uvh --force on:


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

How Reproducible:
Every time

Steps to Reproduce:

As root,
1. cd /usr/src/linux-2.4.9-31
2. make mrproper
3. make xconfig
4. make dep
5. make clean
6. make bzImage

Actual Results:
Segmentation fault while working in random sub-directories of the
'drivers' directory.

Expected Results:
make bzImage shuold have completed without error.

Additional Information:
Motherboard is a PAG2130 from FIC.
Initial install of the RH7.2 distribution on this machine was normal.
This system has been maintained using the up2date facility.
Comment 1 Jakub Jelinek 2002-04-04 07:15:26 EST
Random non-reproduceable compiler crashes means hardware errors.
Please check your memory (e.g. memtest86), CPU, board.

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