Hi,
On Tue, Aug 16, 2005 at 10:19:14AM +0200, Remco Barendse
wrote:> Hi list!
>
>
> The box was installed only yesterday. Yesterday I was still able to compil
> stuff, yesterday even the tiniest and simplest programs fail to compile
> always with internal compiler error: Segmentation fault.
>
> The 'funny' thing is that the problem is in different modules for
each
> program like:
> /usr/include/stdlib.h:757: internal compiler error: Segmentation fault
> include/linux/posix_types.h:41: internal compiler error: Segmentation
> /usr/include/gconv.h:72: internal compiler error:
>
> Any ideas as to what might be broken on the box?
>
>From experience i'd say few things might be the problem
a) incompatible memory or too tight timings for dual channel to work
properly (if it's dual-channel). I for example have to reduce timing on
one dual-core Athlon64 from 1T to 2T or the box isn't stable even with
lowered (manually) DDR-speeds. Not even with BH-5 chips.
b) CPU itself is overheating which makes gcc internal checking fail.
This should manifest itself differently tho (the signal 11 syndfrome).
I do remember having those segfaults with too tight memory timings
sometimes. Usually the box just hard locked every time in less than
hour. The 1GB setup (2x512MB) was fine with any timing if not using
dual-channel, but dual-channel just didn't work with default timings.
The mobo here is DFI LanParty (something PCI-E) which has been happy
with 4x512MB dual-sided DDR-400 (should be reduced to 333 tho) after
diabling the 1T timings.
I can't say that this is the problem, but from the symptoms i'd pretty
much say it is.
--
Pasi Pirhonen - upi at iki.fi - http://iki.fi/upi/