1 |
Thanks guys, this solved it! I changed the memory timing in bios, but I also |
2 |
disabled "apic", so I really don't know which of them did it, but I will |
3 |
re-enable them one at a time to check (later on...) |
4 |
|
5 |
----- Original Message ----- |
6 |
From: "Duncan" <1i5t5.duncan@×××.net> |
7 |
To: <gentoo-amd64@l.g.o> |
8 |
Sent: Tuesday, September 26, 2006 8:06 AM |
9 |
Subject: [gentoo-amd64] Re: problems with emerging programs |
10 |
|
11 |
|
12 |
> "Richard Fish" <bigfish@××××××××××.org> posted |
13 |
> 7573e9640609251725q52cf39efr58d0f59dfb15ce5b@××××××××××.com, excerpted |
14 |
> below, on Mon, 25 Sep 2006 17:25:50 -0700: |
15 |
> |
16 |
>> On 9/25/06, Patric Douhane <patric@×××××.se> wrote: |
17 |
>>> That didn't help. But I have some more info on my problem though, found |
18 |
>>> this line when trying to emerge mozilla-firefox: |
19 |
>>> |
20 |
>>> "./loadmsgcat.c: 1295: internal compiler error: Segmentation fault" |
21 |
>>> |
22 |
>>> Hope someone can interprete it... |
23 |
>> |
24 |
>> Every time I've seen this message on my systems, it has been the result |
25 |
>> of |
26 |
>> flakey hardware, particularly memory. Nothing stresses the memory system |
27 |
>> quite like compiling. |
28 |
>> |
29 |
>> If the system works otherwise, I suspect flaky memory timings. Try |
30 |
>> backing those off (in the BIOS), and see if the problems disappear. |
31 |
>> |
32 |
>> And of course, if you are overclocking anything, stop! |
33 |
> |
34 |
> 100% agreed! I used to have some borderline generic memory, rated pc3200 |
35 |
> (400 MHz), that wasn't quite stable at that. The trouble was my machine |
36 |
> didn't at that time have a BIOS with memory timing limit capacities, so it |
37 |
> was clocked what it was rated and that was that. |
38 |
> |
39 |
> After suffering with it for awhile, I discovered they had a new BIOS |
40 |
> update out which allowed memory timing limits. Setting it to limit @ 183 |
41 |
> MHz (DDRed to 366), I guess PC3000, it was stable as a rock, no problems |
42 |
> whatsoever, until I upgraded to 8 gig awhile later. |
43 |
> |
44 |
> Anyway, while it would occasionally freeze the machine, doing whatever, |
45 |
> the worst was bunzip2ing and compiling. Those would segfault frequently |
46 |
> enough that I had to babysit all my emerges, and learn how to restart in |
47 |
> the middle of them instead of starting over. So yes, definitely, if gcc |
48 |
> is segfaulting, that's a very strong hint of a hardware problem. |
49 |
> |
50 |
> Note that memory is one possibility, but another strong candidate is bad |
51 |
> power, either due to a bad (or underpowered) computer power supply, or in |
52 |
> one case that came up on the lists, an underpowered UPS, or possibly |
53 |
> simply bad incoming power. So in addition to checking memory, verify your |
54 |
> entire power system, from the wall, thru your UPS (if you don't have one, |
55 |
> try one, but make sure it's high enough powered), thru your computer power |
56 |
> supply itself. Low power's the equivalent of clocking beyond stable, in |
57 |
> that the effect is occasional zeros where there should be ones. And yes, |
58 |
> it's gcc and bzip2 (well bunzip2) that seem most sensitive to it. |
59 |
> |
60 |
> On the bright side, when there was a problem, gcc would segfault or |
61 |
> there'd be other errors. I never had an issue with bad builds due to the |
62 |
> memory. It either built right, or it failed to complete the build at all. |
63 |
> |
64 |
> -- |
65 |
> Duncan - List replies preferred. No HTML msgs. |
66 |
> "Every nonfree program has a lord, a master -- |
67 |
> and if you use the program, he is your master." Richard Stallman |
68 |
> |
69 |
> -- |
70 |
> gentoo-amd64@g.o mailing list |
71 |
> |
72 |
|
73 |
|
74 |
-- |
75 |
gentoo-amd64@g.o mailing list |