Re: Re: Compileing 2.0.33pl1 or 2.1.124
Yello
Petr Stehlik:
>> gcc: Internal compiler error: program cc1 got fatal signal 11
> but this is fatal - people say that signal 11 means either bad memory
(RAM)
> or bad harddrive (if swapping) or bad CPU (if overclocked - probably not
> your case).
> There's a long description of signal 11 somewhere on the net describing
why
> hardware problems are detected by gcc.
Peter Missel:
>Fatal Signal 11 is the classic response to a hidden hardware problem.
>Getting it from gcc on an otherwise well running system indicates a DRAM
problem, as gcc is >about the largest application you can have. Other
typical sources of this problem are flaky SCSI >(bad cable, wrong setup,
out-of-spec cabling or termination) or, in x86 environments, CPUs with >a
bug in them.
Arghhhh..... Hardware error.......O my god.....
Well some times Linux m68k just hangs, no "ctrl c/z" works, and I can't
change to another console.
And the "Ctrl Amiga Amiga" just resets the machine.....
Well it's a old A4000, with 16MB ram, of which 2 of the 4mb banks are 30pins
modules in a "simverter", can that be the problem, it works fine with
AmigaOS, and when emulating MacOS...
I also had a problem with my old 1 GB harddrive, it got more and more
errors, now I use it as a backup drive and no errors happen......
Now is there a solusion to my problem, or should I go get a new
machine.....?
Thanx for your time,
--
Henrik Th. Farre
<tsb>Boykot MSN Hotmail
<sb>
Amiga4000 - 040 - 16MB - CyberVision64/3D - Eizo F56 17" Monitor
3.2GB Quantum Fireball - 33.6 kbs modem
AmigaOS 3.1 - MacOS 7.6.1 - Linux Debian 2.0
<tsb>Contact
*homepage 1: http://welcome.to/Webbench*
homepage 2: www.Crosswinds.net/denmark/~enrique
*e-mail 1: mad_enrique@usa.net *
e-mail 2: enrique@denmark.crosswinds.net
<sb>
Reply to: