Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 409279 - www-client/firefox-10.0.1-r1 - ./../../dist/include/js/HashTable.h:914:35: internal compiler error: Segmentation fault
Summary: www-client/firefox-10.0.1-r1 - ./../../dist/include/js/HashTable.h:914:35: in...
Status: RESOLVED DUPLICATE of bug 20600
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: Gentoo Toolchain Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-22 08:33 UTC by Alexander Hartner
Modified: 2013-01-15 12:02 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
Output for emerge --info (emerge-info.txt,3.95 KB, text/plain)
2012-03-22 08:33 UTC, Alexander Hartner
Details
Output of emerge -pqv (emerge-out.txt,740 bytes, text/plain)
2012-03-22 08:34 UTC, Alexander Hartner
Details
Emerge log (emerge-run.txt,232.61 KB, text/plain)
2012-03-22 08:34 UTC, Alexander Hartner
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Hartner 2012-03-22 08:33:45 UTC
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.
Comment 1 Alexander Hartner 2012-03-22 08:34:31 UTC
Created attachment 306265 [details]
Output of emerge -pqv
Comment 2 Alexander Hartner 2012-03-22 08:34:52 UTC
Created attachment 306267 [details]
Emerge log
Comment 3 Ryan Hill (RETIRED) gentoo-dev 2012-03-23 02:39:27 UTC
If it emerged after several attempts then you're probably looking at a hardware issue.
Comment 4 Alexander Hartner 2012-03-23 02:44:50 UTC
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 ?
Comment 5 Alexander Hartner 2012-03-23 16:13:40 UTC
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.
Comment 6 Ryan Hill (RETIRED) gentoo-dev 2012-03-24 01:44:29 UTC
(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.
Comment 7 SpanKY gentoo-dev 2012-03-24 06:28:17 UTC

*** This bug has been marked as a duplicate of bug 20600 ***