Re: 1.6.32 make problems

Fairlight (fairlite@iglou.com)
Tue, 13 Feb 1996 13:37:55 -0500 (EST)

> > > See the Signal 11 FAQ...
> > >=20
> > > http://einstein.et.tudelft.nl/~wolff/sig11/
> >=20
> > Note that if this always happens in the same place, it sounds like a
> > compiler bug. Those do happen, and if so I'd suggest upgrading to 2.=
> 7.1
> > which is pretty stable (I don't trust 2.7.2, but that is reported to
> > have problems mainly on alpha's, and it should be ok on x86).=20
> > Linus

> I had exactly the same problem with gcc and signal 11 until i changed m=
> y=20
> memory from having 2x60ns plus 2x70ns memory to 4x60ns. Then it=20
> worked fine. I'm using gcc 2.7.0 and i don't think it's a compilerbug.

I can second this opinion. I've used 2.6.2 for ages now. When I first
upgraded from a 486 dx33 to a dx4/120 and got a new motherboard, I found I
started getting signal 11's when I compiled anything, including the kernel.

I went into the BIOS settings and changed the DRAM speed a notch slower,
and the signal 11 problems stopped. Oh, and I think I had to change the
burst speed too.

Generally, I think if your system is going too fast for your memory, that's
when you get signal 11 on compiles.

mark->

-- 
Fairlight->   |||        fairlite@iglou.com          | Fairlight Consulting
  __/\__      ||| "I'm talking for free...           | http://www.fairlite.com
 <__<>__>     |||   It's a New Religion..."          | info@fairlite.com
    \/        ||| PGP Public Key available via finger @iglou, or Key servers