| View previous topic :: View next topic |
| Author |
Message |
taskara
Advocate
Joined: 10 Apr 2002
Posts: 3763
Location: Australia
|
 Posted: Tue Apr 23, 2002 1:20 pm Post subject: this is the error I get.. |
 |
|
compiling... blahbah
linking... blahblah
collect2: ld terminated with signal 11 [segmentation fault] core dumped
make[1]: *** [imagetops] Error1
make: *** [all] Error 1
!!! Error: The ebuild did not compete successfully
!!! Function: src_compile, line 11, Exitcode 2.
!!! compile problem
aborting blah blah..
so I can't get any further with my gentoo installation.. can't compile X |
|
| Back to top |
|
 |
tod
Developer
Joined: 17 Apr 2002
Posts: 136
Location: Ozarks, USA
|
| Posted: Tue Apr 23, 2002 6:49 pm Post subject: |
|
|
Hi!
"blah" isn't very informative.
tod |
|
| Back to top |
|
|
taskara
Advocate
Joined: 10 Apr 2002
Posts: 3763
Location: Australia
|
| Posted: Tue Apr 23, 2002 10:17 pm Post subject: |
|
|
you're right, blah's not very helpful
but it's different apps each time
sometimes cups
sometimes xf86
I think it's a hardware problem to do with cpu or ram |
|
| Back to top |
|
|
bob_t
n00b
Joined: 18 Apr 2002
Posts: 23
Location: ithaca, ny, usa
|
| Posted: Thu Apr 25, 2002 12:20 am Post subject: |
|
|
| taskara wrote: | | I think it's a hardware problem to do with cpu or ram |
And this from the Gentoo-User list...search the thread to get more information.:
Date: Wed, 24 Apr 2002 04:30:53 +0200 (CEST)
X-Mailer: SquirrelMail (version 1.2.5 [cvs])
From: "Brian Josefsen" <josefsen@>
To: <gentoo-newbies@gentoo.org>
Reply-To: gentoo-newbies@gentoo.org
Subject: Re: [gentoo-newbies] Crash during Install
> Process cc1 (pid: 4447 stackpage=cb03f000)
> ----
> gcc: Internal compiler error: program cc1 got fatal signal 11
> make[3]:*** [syms.lo] Error 1
> make[3]:*** [Waiting for unfinished jobs]
>
> Any assist will be appreciated. Thought things were going good.
>
I'm not 100% on this but i think signal 11 is bad RAM........ |
|
| Back to top |
|
|
taskara
Advocate
Joined: 10 Apr 2002
Posts: 3763
Location: Australia
|
| Posted: Thu Apr 25, 2002 12:59 am Post subject: |
|
|
ok ta.. I'll watch for that in the future..
anywhere were we can find out what errors mean what? ie 11 = bad ram ? |
|
| Back to top |
|
|
reverius42
Apprentice
Joined: 16 Jul 2002
Posts: 166
Location: Tucson, AZ
|
| Posted: Wed Jul 17, 2002 9:47 pm Post subject: Bad RAM |
|
|
| taskara wrote: | you're right, blah's not very helpful
but it's different apps each time
sometimes cups
sometimes xf86
I think it's a hardware problem to do with cpu or ram |
Check your RAM! I've seen bad RAM cause this before. Try MemTest86... it will be able to tell you if you have bad RAM or not.
_________________
Even a stopped clock gives the right time twice a day. |
|
| Back to top |
|
|
rac
Bodhisattva
Joined: 30 May 2002
Posts: 6553
Location: Japanifornia
|
| Posted: Wed Jul 17, 2002 9:59 pm Post subject: Re: Bad RAM |
|
|
| reverius42 wrote: | | Check your RAM! I've seen bad RAM cause this before. |
I agree wholeheartedly.
| Quote: | | Try MemTest86... it will be able to tell you if you have bad RAM or not. |
While it's certainly a nice program, and it will catch some errors, don't make the assumption that just because memtest86 says "OK", then things are OK.
I find a kernel compile loop, accompanied by a bunzip of a huge file (a Gentoo stage 3 tarball is very convenient for this purpose) is a more stressful and realistic memory test suite. Here are a couple of quick-and-dirty shell scripts I used for this purpose recently:
| Code: | #!/bin/sh
set -x
t=1
while [ -f log.$t ]
do
t=`expr $t + 1`
done
while true
do
make clean
make -k bzImage > log.$t
t=`expr $t + 1`
done |
| Code: | #!/bin/sh
set -x
while true
do
rm -rf /var/tmp/stress2/*
cd /var/tmp/stress2
tar xvjpf /home/rac/stage3-i686-1.2.tbz2
done |
I usually ran the second one niced, to allow more kernel compiles. When the bad RAM was in the machine, this would lock things up nicely within 2 or 3 kernel compile cycles, sometimes making even simple programs (like 'rm' and 'shutdown') segfault. Filesystem corruption, you name it.
Once everyone involved was convinced it was the RAM, and it was swapped out, it cranked out 250+ kernel compiles without error in about 18 hours under an consistent CPU load of 3.5 or so. Very dramatic difference.
_________________
For every higher wall, there is a taller ladder |
|
| Back to top |
|
|
taskara
Advocate
Joined: 10 Apr 2002
Posts: 3763
Location: Australia
|
| Posted: Wed Jul 17, 2002 10:06 pm Post subject: |
|
|
thanks.. - found out it was a cpu incompatibility with my mainboard..
so I went to a duron instead of the XP 
but I'll upgrade soon anyway 
and thanks for the memory test tips.. I'll try them out also! |
|
| Back to top |
|
|
rac
Bodhisattva
Joined: 30 May 2002
Posts: 6553
Location: Japanifornia
|
| Posted: Wed Jul 17, 2002 10:14 pm Post subject: |
|
|
| taskara wrote: | | anywhere were we can find out what errors mean what? ie 11 = bad ram ? |
They're signal numbers. You can get a list of them with Once you have their names, googling with them will probably tell you more than you want to know.
_________________
For every higher wall, there is a taller ladder |
|
| Back to top |
|
|
|
Portage & Programming
