Quote:>>>>> Skunk Schouten writes:
>> compiler error: progam cc1 got fatal signal 11
>> >I know of a possible intermittant memory problem. Could this be it?
>> Most likely. Signal 11 seems to be what most people get when gcc barfs
>> on some bad memory.
SS> overheated processor.
[ ... ]
SS> http://einstein.et.tudelft.nl:80/~wolff/sig11/ for a good summary
SS> of what happens.
I can also report at least one (mine !) case of a ill-behaved EIDE hard
I use an ASUS p55tp4xe with a P133 and 256K standard PBurst (think it's
15ns but not checked) ... with 70ns SIMMs (albeit ASUS recommends 60ns
ones) and two 1G EIDE (WD Caviar 21) drives for RAID0 ("md", very good,
It gave very numerous flaws (gcc compilation was impossible) => I disabled
the PBurst cache and all went good.
But one of the EIDE drives was in fact bad (did not dynamically remap bad
I have it changed and the entire thing now works no flawlessly, even
with PBurst on.
Compilations (kernel and gcc) and "memtest" does not reveal any more
problem in an entire afternoon.
I do not know the explanation. Perhaps bus-timings related problems, since
IDE-family drives 'controlers' are bus extensions (?)
But the box is more responsive. The Byte bench performance index is now
15.2, it's a 39% boost (thanks to the RAID0 and PBurst cache) !
[ Followup-To: comp.os.linux.hardware ]