Created attachment 306263 [details]
Output for emerge --info
While trying to emerge mozilla I encountered a segmentation fault. This happened during the installation of a new system. Earlier on in the installation process another segmentation fault occured during the emerge of llvm, however after a reboot and several attempts llvm finally emerged. During the installation of llvm the system froze on what looked like a kernel panic. Unfortunately I did't record the detail of the llvm issue. However now that I am getting further segmentation faults I figured it best to report the issue.
Created attachment 306265 [details]
Output of emerge -pqv
Created attachment 306267 [details]
If it emerged after several attempts then you're probably looking at a hardware issue.
You might be onto something. I enabled XMP (Extreme Memory Profile) in my Bios to get my memory running at 2133Mhz rather then 1600Mhz. Since setting it back to 1600Mhz it seems to be working correctly. Both my motherboard and the memory modules support running at 2133Mhz, however I have to enable XMP for some reason.
Could this be the cause of this issue ?
As suggested on the Gentoo forum (http://forums.gentoo.org/viewtopic-p-6993210.html#6993210) I ran memtest with both XMP enabled / disabled. After two completed test cycles NO errors were found. Right now I am running with XMP disabled. So far so good. Would be nice to leverage the extra speed though.
(In reply to comment #4)
> You might be onto something. I enabled XMP (Extreme Memory Profile) in my
> Bios to get my memory running at 2133Mhz rather then 1600Mhz. Since setting
> it back to 1600Mhz it seems to be working correctly. Both my motherboard and
> the memory modules support running at 2133Mhz, however I have to enable XMP
> for some reason.
> Could this be the cause of this issue ?
Yes. Both mozilla and llvm builds can both put a lot of stress on the memory system. Maybe they exercise it in a way that memtest doesn't. If running it at 1600MHz works then the problem is with your hardware. There's nothing much we can do here.
*** This bug has been marked as a duplicate of bug 20600 ***