Lucid Dream wrote:
>
> I don't suppose this error looks familiar to anyone?
>
Oh yes, it looks sadly familiar to me...
> ----------------------------------------------------------------
> gcc -DTHE_FTAPE_MAINTAINER=\"[EMAIL PROTECTED]\"
> -DBROKEN_FLOPPY_DRIVER -DCONFIG_FT_PROC_FS -DCONFIG_FT_STD_FDC_0
> -DCONFIG_FT_INT_0=1 -DCONFIG_FTAPE_MODULE -DCONFIG_FT_INTERNAL_MODULE
> -DCONFIG_FT_TRAKKER_MODULE -DCONFIG_FT_BPCK_MODULE -DCONFIG_ZFTAPE_MODULE
> -DCONFIG_ZFT_COMPRESSOR_MODULE -D__KERNEL__ -I.
> -I../../include -I/usr/src/linux/include -m486 -malign-loops=2
> -malign-jumps=2 -malign-functions=2 -DCPU=586 -E -D__GENKSYMS__
> ftape_syms.c \
> | /sbin/genksyms ../../include/linux/modules 2> /dev/null; \
> fi
> gcc: Internal compiler error: program cpp got fatal signal 11
Signal 11 means that the processor referenced a memory location which is
inside the legal addressable space of 4 GB that a Pentium can address,
but outside the physically accessible space of the memory actually
installed in the system :-(
The cause of this error _could_ lie in software...but in the case of the
GNU C Compiler, a piece of software that is widely tested and known to
be _very_ stable, this is almost surely not the case.
To put it in one sentence: You have a _serious_ hardware problem,
probably in your memory modules. It could be the timing of the RAM
modules that is too tight. But very probably you simply have a bad RAM
module :-(
Take away half of your RAM (the RAM of one memory bank) and recompile.
If you get Signal 11 again, put it back and take away the other half.
Thus you can locate the bad ones. For a thorough discussion of the
ominous Signal 11 look at the Signal 11 FAQ (yes, there _is_ one, just
do a search and you'll find it easily, I don't have it now here, in my
vacation and internet connectivity costs me an international phone
call).
> My apologies if this is a well-known problem and my tired brain has missed
> an obvious answer.
>
This is not an obvious problem anyway, so don't worry. Consider yourself
lucky that you run Linux, which _can_ detect such a problem - I run
Windows with a bad SIMM for more than a year, having very often crashes
that left my hard disk full of lost chains and the like, destroying
work of days and making me mad for it, until I compiled ftape under
Linux ...and got a Signal 11. It was a bad memory module.
Chris
