Signal 11 and RH6.2

[llewelly@dbritsch.dsl.xmission.com]

On Mon, 10 Jul 2000, Victor wrote:

> Yes, I have done a kernel recompile. With egcs in rh6.2, I got signal 11; with
> 
> gcc 2.95.2 on Turbolinux, I compiled both 2.2.16 and 2.4.0-test2 kernels and I
> 
> am running both without a single problem. I reinstalled redhat couple of
> times. Usually, sig11 only occured on kernel recompiles. However I recall
> where I couldn't even compile ssh and was getting signal 11. GCC would not
> compile using egcs and I got signal 11. However, if the hardware is at fault,
> how do you determine which part and why is everything working flawlessly (as
> far as I know at least) with gcc 2.95.2  and Turbo distro? Turbo, in my view,
> is a complete redhat knockoff and seems to be almost identical to to a redhat
> install (6.1). But turbo has gcc 2.95.2. I don't like this turbo distro
> though, and would much rather run redhat but can't (for obvious reasons).
> 
> Am clueless here. What test can I run on my system to determine what would
> cause signal 11 ???
> 
> I also ran OpenBSD before and didn't have any problems. Why would hardware
> problems only show up now (in rh6.2) ? I would like to figure out if it is
> indeed the compiler or maybe I do have a hardware issue. It seems if it is
> hardware, it can be one of four things: CPU, Chipset, Memory, or motherboard
> (some other component). CPU is not my first guess and I tried two different
> sticks of memory, both of which are tested working memory. So I am left to
> believe it's either a chipset problem or incompatibility of VIA MVP4 and linux
> 
> or linux egc 2.91.66 compiler. Anything I can do here? It's like a catch-22:
> hardware points to software and software blames hardware.
> 

Unfortunately I do not know either.

If you have made any ventilation/temperature changes, that may be the
  reason; I have seen hardware problems disappear that way.