From: n217cg@tamuts.tamu.edu (Scott Taylor) Subject: Re: gcc: Internal compiler error: program cc1 got fatal signal 11 (AGAIN) Date: 21 Sep 1992 00:23:13 GMT
In article <1992Sep20.095952.7079@ucsu.Colorado.EDU> ngoh@rintintin.Colorado.EDU (NGO HIEN D) writes:
>In article <68445@hydra.gatech.EDU> kheldar@prism.gatech.EDU (Garner) writes:
>>In article <BurF59.Bu7@ux1.cso.uiuc.edu> Upholder@uiuc.edu (THE Upholder of Truth) writes:
>>->Everything I try to compile, including hello.c dies with the following
>>->error:
>>->
>>-> gcc: Internal Compiler error: program cc1 got fatal signal 11
>>
>
>funny you should mention this problem. I have been running Linux on
> ...problem deleted...
>forget running anything for long without the flakey errors.
>
>Anyone have a clue as to why this would happen?
>
Just a random shot in the dark, but are you using a SCSI disk? I remember
reading somewhere that there was a problem with certain SCSI controllers
(Seagate, at least) having their I/O port addresses cacheable. In other
words, if the addresses corresponding to the controller's I/O ports were
cached, problems resulted. The solution was to go into the BIOS setup
program and mark the set of addresses which include the SCSI adapter I/O
ports as non-cacheable.
>My complete setup: 386/40, 4megs memory, linux 0.97pl5 (sound blaster
>compiled into kernel).
>
>I've tried adding waitstates to the cache, memory, changing
>shadowing options, but I am almost 100% certain that the
>cache is the culprit. I will take the previous poster's
>suggestion and try the machine with more memory and see if
>that solves anything.
>
Besides the above, I have no idea. Maybe the designers of your motherboard
never expected it to run anything but DOS and MS Windoze ;-)
>Hien D. Ngo
>ngoh@rtt.colorado.edu
Scott Taylor
n217cg@tamuts.tamu.edu