* [gentoo-user] emerge troubles
@ 2006-02-14 10:38 Jorge Almeida
2006-02-14 14:50 ` Benno Schulenberg
0 siblings, 1 reply; 21+ messages in thread
From: Jorge Almeida @ 2006-02-14 10:38 UTC (permalink / raw
To: gentoo-user
I'm unable to emerge gcc:
17012 all allocated states, 101385 all allocated arcs
20258 all allocated alternative states
4765 all transition comb vector els, 13107 all trans table els
4765 all state alts comb vector els, 13107 all state alts table els
13107 all min delay table els
0 locked states num
transformation: 0.016001, building DFA: 7.968497
DFA minimization: 0.468029, making insn equivalence: 0.000000
all automaton generation: 8.536533, output: 0.144009
/bin/sh /var/tmp/portage/gcc-3.4.4-r1/work/gcc-3.4.4/gcc/move-if-change tmp-attrtab.c insn-attrtab.c
echo timestamp > s-attrtab
stage1/xgcc -Bstage1/ -B/usr/i686-pc-linux-gnu/bin/ -O2 -march=pentium4 -pipe -fprofile-generate -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wold-style-definition -DHAVE_CONFIG_H -I. -I. -I/var/tmp/portage/gcc-3.4.4-r1/work/gcc-3.4.4/gcc -I/var/tmp/portage/gcc-3.4.4-r1/work/gcc-3.4.4/gcc/. -I/var/tmp/portage/gcc-3.4.4-r1/work/gcc-3.4.4/gcc/../include -c insn-attrtab.c \
-o insn-attrtab.o
cc1: out of memory allocating 8579592 bytes after a total of 7716864 bytes
make[2]: *** [insn-attrtab.o] Error 1
make[2]: Leaving directory `/var/tmp/portage/gcc-3.4.4-r1/work/build/gcc'
make[1]: *** [stageprofile_build] Error 2
make[1]: Leaving directory `/var/tmp/portage/gcc-3.4.4-r1/work/build/gcc'
make: *** [profiledbootstrap] Error 2
!!! ERROR: sys-devel/gcc-3.4.4-r1 failed.
!!! Function gcc_do_make, Line 1339, Exitcode 2
!!! emake failed with profiledbootstrap
!!! If you need support, post the topmost build error, NOT this status message.
The problem appeared when emerging -DNu world. It failed with kpdf. Then
I tried to emerge binutils glibc gcc and it failed at gcc.
Assuming a hardware problem, I tried a script I read about on a recent
thread:
http://people.redhat.com/dledford/memtest.html
The script executed without a whisper.
The box has 1GB RAM, P4 3GHz, no overclocking. The system is up to date.
revdep-rebuild seems happy, except for wanting to re-emerge
openoffice-bin, always.
What else can I do? Is there some other test for hw failure? I can't try
memtest now (I'm away from the box) but it didn't report errors last time
I checked, not too long ago.
--
Jorge Almeida
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [gentoo-user] emerge troubles
2006-02-14 10:38 [gentoo-user] emerge troubles Jorge Almeida
@ 2006-02-14 14:50 ` Benno Schulenberg
2006-02-14 18:12 ` Jorge Almeida
0 siblings, 1 reply; 21+ messages in thread
From: Benno Schulenberg @ 2006-02-14 14:50 UTC (permalink / raw
To: gentoo-user
Jorge Almeida wrote:
> cc1: out of memory allocating 8579592 bytes after a total of
> 7716864 bytes
Swap not enabled? Also, emerge --info output would be helpful.
Benno
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [gentoo-user] emerge troubles
2006-02-14 14:50 ` Benno Schulenberg
@ 2006-02-14 18:12 ` Jorge Almeida
2006-02-14 20:43 ` Benno Schulenberg
0 siblings, 1 reply; 21+ messages in thread
From: Jorge Almeida @ 2006-02-14 18:12 UTC (permalink / raw
To: gentoo-user
On Tue, 14 Feb 2006, Benno Schulenberg wrote:
> Jorge Almeida wrote:
>> cc1: out of memory allocating 8579592 bytes after a total of
>> 7716864 bytes
>
> Swap not enabled? Also, emerge --info output would be helpful.
>
Swap was enabled.
$ emerge info
Portage 2.0.54 (default-linux/x86/2005.1, gcc-3.4.4, glibc-2.3.5-r2, 2.6.14-gentoo-r2 i686)
=================================================================
System uname: 2.6.14-gentoo-r2 i686 Intel(R) Pentium(R) 4 CPU 3.00GHz
Gentoo Base System version 1.6.14
dev-lang/python: 2.3.5, 2.4.2
sys-apps/sandbox: 1.2.12
sys-devel/autoconf: 2.13, 2.59-r6
sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils: 2.16.1
sys-devel/libtool: 1.5.22
virtual/os-headers: 2.6.11-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O2 -march=pentium4 -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -march=pentium4 -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks sandbox sfperms strict"
GENTOO_MIRRORS="ftp://ftp.rnl.ist.utl.pt/pub/gentoo http://distfiles.gentoo.org http://www.ibiblio.org/pub/Linux/distributions/gentoo"
LANG="en_US"
MAKEOPTS="-j1"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="x86 X aalib acpi bash-completion bitmap-fonts bzip2 cdb cdparanoia cdr crypt cups curl gif gtk gtk2 imap imlib java jpeg jpeg2k kde maildir motif ncurses nls nptl nsplugin opengl pam pdflib perl pic png posix python qt readline recode ssl tiff truetype truetype-fonts type1-fonts xml zlib userland_GNU kernel_linux elibc_glibc"
Unset: ASFLAGS, CTARGET, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
--
Jorge Almeida
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [gentoo-user] emerge troubles
2006-02-14 18:12 ` Jorge Almeida
@ 2006-02-14 20:43 ` Benno Schulenberg
2006-02-14 21:10 ` Jorge Almeida
0 siblings, 1 reply; 21+ messages in thread
From: Benno Schulenberg @ 2006-02-14 20:43 UTC (permalink / raw
To: gentoo-user
Jorge Almeida wrote:
> Swap was enabled.
> $ emerge info
> [...]
Looks fine.
Have you tried emerging gcc again, a few times, and does it fail
every time in the same spot with the same error? What error does
kpdf give? Does it too fail every time at the same place? Have
you tried closing memory-hungry apps like Firefox? Have you maybe
changed the memory timings in the BIOS lately? Perhaps it is time
to dust off the computer on the inside and reseat the mem chips?
Benno
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [gentoo-user] emerge troubles
2006-02-14 20:43 ` Benno Schulenberg
@ 2006-02-14 21:10 ` Jorge Almeida
2006-02-14 23:43 ` Benno Schulenberg
0 siblings, 1 reply; 21+ messages in thread
From: Jorge Almeida @ 2006-02-14 21:10 UTC (permalink / raw
To: gentoo-user
On Tue, 14 Feb 2006, Benno Schulenberg wrote:
> Jorge Almeida wrote:
>> Swap was enabled.
>> $ emerge info
>> [...]
>
> Looks fine.
>
> Have you tried emerging gcc again, a few times, and does it fail
> every time in the same spot with the same error? What error does
Yes. I tried with CFLAGS and CXXFLAGS="", and with MAKEOPTS="-j1".
> kpdf give? Does it too fail every time at the same place? Have
config.status: executing depfiles commands
Good - your configure finished. Start make now
make all-recursive
make[1]: Entering directory `/var/tmp/portage/kpdf-3.4.3-r4/work/kpdf-3.4.3'
Making all in doc
make[2]: Entering directory `/var/tmp/portage/kpdf-3.4.3-r4/work/kpdf-3.4.3/doc'
Making all in kpdf
make[3]: Entering directory `/var/tmp/portage/kpdf-3.4.3-r4/work/kpdf-3.4.3/doc/kpdf'
/usr/kde/3.4/bin/meinproc --check --cache index.cache.bz2 ./index.docbook
parser error : out of memory error
parser error : out of memory error
/bin/sh: line 1: 3831 Segmentation fault /usr/kde/3.4/bin/meinproc --check --cache index.cache.bz2 ./index.docbook
make[3]: *** [index.cache.bz2] Error 139
make[3]: Leaving directory `/var/tmp/portage/kpdf-3.4.3-r4/work/kpdf-3.4.3/doc/kpdf'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/kpdf-3.4.3-r4/work/kpdf-3.4.3/doc'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/kpdf-3.4.3-r4/work/kpdf-3.4.3'
make: *** [all] Error 2
!!! ERROR: kde-base/kpdf-3.4.3-r4 failed.
!!! Function kde_src_compile, Line 217, Exitcode 2
!!! died running emake, kde_src_compile:make
!!! If you need support, post the topmost build error, NOT this status message.
(Always at the same place.)
> you tried closing memory-hungry apps like Firefox? Have you maybe
No memory-hungry apps are open, since I'm working through ssh (and there
are no other human users).
> changed the memory timings in the BIOS lately? Perhaps it is time
Never touched that. The computer is about 1 year old (but I think the
RAM is generic, so I would think about bad RAM, only I can't confirm it
through testing...)
> to dust off the computer on the inside and reseat the mem chips?
Perhaps, but that's a somewhat frightening idea!
>
> Benno
>
Thanks.
Jorge
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [gentoo-user] emerge troubles
2006-02-14 21:10 ` Jorge Almeida
@ 2006-02-14 23:43 ` Benno Schulenberg
2006-02-14 23:57 ` Zac Slade
0 siblings, 1 reply; 21+ messages in thread
From: Benno Schulenberg @ 2006-02-14 23:43 UTC (permalink / raw
To: gentoo-user
Jorge Almeida wrote:
> parser error : out of memory error
> /bin/sh: line 1: 3831 Segmentation fault
Doesn't look good. :(
> No memory-hungry apps are open, since I'm working through ssh
> (and there are no other human users).
Is this box always on? Have you tried rebooting? Maybe loads of
memory have leaked away.
> > to dust off the computer on the inside and reseat the mem
> > chips?
>
> Perhaps, but that's a somewhat frightening idea!
If the RAM has gone bad, to replace it you will have to touch it
anyway. So, no harm in trying to wriggle it a bit first. Touch
and hold the case before touching the RAM strips.
Benno
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [gentoo-user] emerge troubles
2006-02-14 23:43 ` Benno Schulenberg
@ 2006-02-14 23:57 ` Zac Slade
2006-02-15 1:25 ` Jorge Almeida
0 siblings, 1 reply; 21+ messages in thread
From: Zac Slade @ 2006-02-14 23:57 UTC (permalink / raw
To: gentoo-user
On Tuesday 14 February 2006 17:43, Benno Schulenberg wrote:
> Jorge Almeida wrote:
> > parser error : out of memory error
> > /bin/sh: line 1: 3831 Segmentation fault
>
> Doesn't look good. :(
No it doesn't, but there has to be a reason why he's out of memory... What is
the output of free, before emerge? How about after it fails? Can you give
the output of the following commands:
cat /proc/sys/vm/swappiness
cat /proc/sys/vm/overcommit_memory
cat /proc/sys/vm/overcommit_ratio
Also try using "vmstat 5" in one window and attempting the emerge in another
window.
What process is using the most memory right now? (Check top sorted by
memory).
> Is this box always on? Have you tried rebooting? Maybe loads of
> memory have leaked away.
WHOA! Stop right there. Perhaps we should help him diagnose his problem
before using a shotgun.
> If the RAM has gone bad, to replace it you will have to touch it
> anyway. So, no harm in trying to wriggle it a bit first. Touch
> and hold the case before touching the RAM strips.
There is nothing in the information he has presented thus far to show that
there are memory errors of any type. He very well may be just running out of
memory. It happens.
Send back the extra information and let's get to the bottom of the issue.
--
Zac Slade
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [gentoo-user] emerge troubles
2006-02-14 23:57 ` Zac Slade
@ 2006-02-15 1:25 ` Jorge Almeida
2006-02-15 1:45 ` Zac Slade
2006-02-15 1:51 ` Richard Fish
0 siblings, 2 replies; 21+ messages in thread
From: Jorge Almeida @ 2006-02-15 1:25 UTC (permalink / raw
To: gentoo-user
On Tue, 14 Feb 2006, Zac Slade wrote:
> On Tuesday 14 February 2006 17:43, Benno Schulenberg wrote:
>> Jorge Almeida wrote:
>>> parser error : out of memory error
>>> /bin/sh: line 1: 3831 Segmentation fault
>>
>> Doesn't look good. :(
> No it doesn't, but there has to be a reason why he's out of memory... What is
> the output of free, before emerge? How about after it fails? Can you give
> the output of the following commands:
> cat /proc/sys/vm/swappiness
> cat /proc/sys/vm/overcommit_memory
> cat /proc/sys/vm/overcommit_ratio
>
$ cat /proc/sys/vm/swappiness
60
$ cat /proc/sys/vm/overcommit_memory
0
$ cat /proc/sys/vm/overcommit_ratio
50
$ free
total used free shared buffers cached
Mem: 1035204 968140 67064 0 270248 538412
-/+ buffers/cache: 159480 875724
Swap: 996020 300 995720
Of course, this is the output of free _after_ the previous failed emerge attempts.
It seems RAM really was caught and not released... I can try rebooting,
but there is the possibility that the box won't boot, and I'm away...
Is there some way to find what's eating RAM?
> Also try using "vmstat 5" in one window and attempting the emerge in another
> window.
>
> What process is using the most memory right now? (Check top sorted by
> memory).
$ top
top - 01:21:23 up 22 days, 17:29, 2 users, load average: 0.00, 0.00, 0.00
Tasks: 120 total, 2 running, 118 sleeping, 0 stopped, 0 zombie
Cpu(s): 0.0% us, 0.0% sy, 0.0% ni, 99.7% id, 0.0% wa, 0.3% hi, 0.0% si
Mem: 1035204k total, 968760k used, 66444k free, 270684k buffers
Swap: 996020k total, 300k used, 995720k free, 538452k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
8291 root 15 0 159m 29m 3056 S 0.0 3.0 5:05.74 X
24756 jorge 15 0 30592 25m 2576 S 0.0 2.5 0:06.52 pine
28731 jorge 16 0 20016 14m 14m S 0.0 1.4 0:19.34 imap
26923 root 15 0 21236 12m 9704 S 0.0 1.2 0:00.39 kdm_greet
24757 jorge 16 0 8436 6292 5984 S 0.0 0.6 0:01.85 imap
21961 jorge 16 0 8044 3992 2684 S 0.0 0.4 0:00.15 vim
8259 root 16 0 5756 2852 1356 S 0.0 0.3 0:50.69 cupsd
24734 root 16 0 5944 1764 1440 S 0.0 0.2 0:00.01 sshd
24767 root 16 0 5948 1764 1440 S 0.0 0.2 0:00.01 sshd
3588 root 15 0 2644 1560 1172 S 0.0 0.2 0:00.11 bash
24746 jorge 15 0 2924 1472 1164 S 0.0 0.1 0:00.02 bash
6396 privoxy 15 0 36028 1464 784 S 0.0 0.1 0:07.90 privoxy
24785 jorge 15 0 2796 1456 1156 S 0.0 0.1 0:00.01 bash
24799 root 16 0 2664 1456 1156 S 0.0 0.1 0:00.00 bash
Jorge Almeida
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [gentoo-user] emerge troubles
2006-02-15 1:25 ` Jorge Almeida
@ 2006-02-15 1:45 ` Zac Slade
2006-02-15 1:56 ` Richard Fish
2006-02-15 2:10 ` Jorge Almeida
2006-02-15 1:51 ` Richard Fish
1 sibling, 2 replies; 21+ messages in thread
From: Zac Slade @ 2006-02-15 1:45 UTC (permalink / raw
To: gentoo-user
On Tuesday 14 February 2006 19:25, Jorge Almeida wrote:
> $ cat /proc/sys/vm/swappiness
> 60
> $ cat /proc/sys/vm/overcommit_memory
> 0
> $ cat /proc/sys/vm/overcommit_ratio
> 50
That was a long shot, but just wanted to make sure the system was allowing
overcommit.
> $ free
> total used free shared buffers cached
> Mem: 1035204 968140 67064 0 270248 538412
> -/+ buffers/cache: 159480 875724
> Swap: 996020 300 995720
This seems within spec. You have plenty of memory free.
> Of course, this is the output of free _after_ the previous failed emerge
> attempts. It seems RAM really was caught and not released... I can try
> rebooting, but there is the possibility that the box won't boot, and I'm
> away... Is there some way to find what's eating RAM?
If you don't have physical access to the system, don't reboot it. It's not
just a good rule of thumb, it's one you should live by (whenever possible).
> > What process is using the most memory right now? (Check top sorted by
> > memory).
>
> $ top
> top - 01:21:23 up 22 days, 17:29, 2 users, load average: 0.00, 0.00,
> 0.00 Tasks: 120 total, 2 running, 118 sleeping, 0 stopped, 0 zombie
> Cpu(s): 0.0% us, 0.0% sy, 0.0% ni, 99.7% id, 0.0% wa, 0.3% hi, 0.0%
> si Mem: 1035204k total, 968760k used, 66444k free, 270684k buffers
> Swap: 996020k total, 300k used, 995720k free, 538452k cached
>
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
> 8291 root 15 0 159m 29m 3056 S 0.0 3.0 5:05.74 X
> 24756 jorge 15 0 30592 25m 2576 S 0.0 2.5 0:06.52 pine
> 28731 jorge 16 0 20016 14m 14m S 0.0 1.4 0:19.34 imap
> 26923 root 15 0 21236 12m 9704 S 0.0 1.2 0:00.39 kdm_greet
> 24757 jorge 16 0 8436 6292 5984 S 0.0 0.6 0:01.85 imap
> 21961 jorge 16 0 8044 3992 2684 S 0.0 0.4 0:00.15 vim
> 8259 root 16 0 5756 2852 1356 S 0.0 0.3 0:50.69 cupsd
> 24734 root 16 0 5944 1764 1440 S 0.0 0.2 0:00.01 sshd
> 24767 root 16 0 5948 1764 1440 S 0.0 0.2 0:00.01 sshd
> 3588 root 15 0 2644 1560 1172 S 0.0 0.2 0:00.11 bash
> 24746 jorge 15 0 2924 1472 1164 S 0.0 0.1 0:00.02 bash
> 6396 privoxy 15 0 36028 1464 784 S 0.0 0.1 0:07.90 privoxy
> 24785 jorge 15 0 2796 1456 1156 S 0.0 0.1 0:00.01 bash
> 24799 root 16 0 2664 1456 1156 S 0.0 0.1 0:00.00 bash
Well nothing really stands out here.... There are multiple imap processes
open, but really you have plenty of memory.
Just an absolute blind stab in the dark..... what does df -h give you?
Anything interesting in dmesg? And just to make sure we have PLENTY of
information here, can we get the end of emerge.log (some context prior to the
error message).
--
Zac Slade
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [gentoo-user] emerge troubles
2006-02-15 1:25 ` Jorge Almeida
2006-02-15 1:45 ` Zac Slade
@ 2006-02-15 1:51 ` Richard Fish
1 sibling, 0 replies; 21+ messages in thread
From: Richard Fish @ 2006-02-15 1:51 UTC (permalink / raw
To: gentoo-user
On 2/14/06, Jorge Almeida <jalmeida@math.ist.utl.pt> wrote:
> $ free
> total used free shared buffers cached
> Mem: 1035204 968140 67064 0 270248 538412
> -/+ buffers/cache: 159480 875724
> Swap: 996020 300 995720
>
> Of course, this is the output of free _after_ the previous failed emerge attempts.
> It seems RAM really was caught and not released... I can try rebooting,
No, it wasn't. The important line is the "+/- buffers/cache", which
shows you have 850M free. The rest of your used memory is buffers or
cached programs, all of which can be swapped back out.
-Richard
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [gentoo-user] emerge troubles
2006-02-15 1:45 ` Zac Slade
@ 2006-02-15 1:56 ` Richard Fish
2006-02-15 2:14 ` Jorge Almeida
2006-02-15 2:10 ` Jorge Almeida
1 sibling, 1 reply; 21+ messages in thread
From: Richard Fish @ 2006-02-15 1:56 UTC (permalink / raw
To: gentoo-user
On 2/14/06, Zac Slade <krakrjak@volumehost.net> wrote:
> Just an absolute blind stab in the dark..... what does df -h give you?
> Anything interesting in dmesg? And just to make sure we have PLENTY of
> information here, can we get the end of emerge.log (some context prior to the
> error message).
Also, to test whether your system can make large memory allocations, you can do:
python -c "s='x'*(4*(1024*1024))"
python -c "s='x'*(8*(1024*1024))"
python -c "s='x'*(16*(1024*1024))"
python -c "s='x'*(32*(1024*1024))"
python -c "s='x'*(64*(1024*1024))"
python -c "s='x'*(128*(1024*1024))"
python -c "s='x'*(256*(1024*1024))"
The above commands will try to allocate memory from 4M to 256M.
-Richard
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [gentoo-user] emerge troubles
2006-02-15 1:45 ` Zac Slade
2006-02-15 1:56 ` Richard Fish
@ 2006-02-15 2:10 ` Jorge Almeida
1 sibling, 0 replies; 21+ messages in thread
From: Jorge Almeida @ 2006-02-15 2:10 UTC (permalink / raw
To: gentoo-user
On Tue, 14 Feb 2006, Zac Slade wrote:
> Just an absolute blind stab in the dark..... what does df -h give you?
$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/hda3 2.0G 281M 1.7G 15% /
udev 506M 300K 506M 1% /dev
/dev/hda5 2.0G 338M 1.6G 18% /var
/dev/hda6 9.9G 3.6G 5.8G 39% /usr
/dev/hdb2 7.6G 3.0G 4.2G 42% /home
/dev/hdb6 23G 6.3G 16G 30% /home/jorge/bulk
/dev/hdb1 7.8G 1.6G 5.9G 21% /home/jorge/bulk/backup
/dev/hda7 2.0G 392M 1.5G 21% /local
/dev/hda8 10G 1.4G 8.6G 15% /local/mail
/dev/hdb3 7.6G 5.8G 1.4G 81% /local/port
/local/port/portage 7.6G 5.8G 1.4G 81% /usr/portage
/local/port/var_tmp 7.6G 5.8G 1.4G 81% /var/tmp/portage
/local/run/qmail/varqmail
2.0G 392M 1.5G 21% /var/qmail
/local/usr 2.0G 392M 1.5G 21% /usr/local
shm 506M 0 506M 0% /dev/shm
> Anything interesting in dmesg? And just to make sure we have PLENTY of
the bottom of dmesg seems strange:
EXT3-fs: mounted filesystem with ordered data mode.
hw_random: RNG not detected
r8169: eth0: link up
ip_tables: (C) 2000-2002 Netfilter core team
ip_conntrack version 2.3 (8191 buckets, 65528 max) - 216 bytes per conntrack
ipt_recent v0.3.1: Stephen Frost <sfrost@snowman.net>. http://snowman.net/projects/ipt_recent/
ipt_owner: pid, sid and command matching not supported anymore
spurious 8259A interrupt: IRQ7.
ipt_owner: pid, sid and command matching not supported anymore
ipt_owner: pid, sid and command matching not supported anymore
ipt_owner: pid, sid and command matching not supported anymore
ipt_owner: pid, sid and command matching not supported anymore
(Many repeated lines like the latter.)
> information here, can we get the end of emerge.log (some context prior to the
> error message).
I suppose you mean the output of emerge? The contents of
/var/log/emerge.log are laconic. Here it goes:
In file included from /var/tmp/portage/gcc-3.4.4-r1/work/gcc-3.4.4/gcc/libgcov.c:37:
/var/tmp/portage/gcc-3.4.4-r1/work/gcc-3.4.4/gcc/tsystem.h:40:1: warning: this is the location of the previous definition
/var/tmp/portage/gcc-3.4.4-r1/work/gcc-3.4.4/gcc/doc//cppopts.texi:137: warning: @strong{Note...} produces a spurious cross-reference in Info; reword to avoid that.
/var/tmp/portage/gcc-3.4.4-r1/work/gcc-3.4.4/gcc/doc//cppopts.texi:345: warning: @strong{Note...} produces a spurious cross-reference in Info; reword to avoid that.
mv: cannot stat `libgcc/*.os': No such file or directory
mv: cannot stat `s-crt0': No such file or directory
mv: cannot stat `crtbegin.o': No such file or directory
mv: cannot stat `crtbeginS.o': No such file or directory
mv: cannot stat `crtbeginT.o': No such file or directory
mv: cannot stat `crtend.o': No such file or directory
mv: cannot stat `crtendS.o': No such file or directory
mv: cannot stat `gcc-cross': No such file or directory
mv: cannot stat `protoize': No such file or directory
mv: cannot stat `unprotoize': No such file or directory
mv: cannot stat `specs': No such file or directory
mv: cannot stat `collect2': No such file or directory
mv: cannot stat `gcov': No such file or directory
mv: cannot stat `gcov-dump': No such file or directory
mv: cannot stat `*.[0-9][0-9].*': No such file or directory
mv: cannot stat `*.[si]': No such file or directory
mv: cannot stat `g++-cross': No such file or directory
mv: cannot stat `cc1plus': No such file or directory
make[2]: [stage1-start] Error 1 (ignored)
cp: cannot stat `libunwind.a': No such file or directory
cp: cannot stat `libunwind*.so': No such file or directory
make[2]: [stage1-start] Error 1 (ignored)
mv: cannot stat `cp/*.o': No such file or directory
make[2]: [c++.stage1] Error 1 (ignored)
gengtype-lex.c: In function `yy_get_next_buffer':
gengtype-lex.c:2412: warning: old-style parameter declaration
gengtype-lex.c: In function `yy_get_previous_state':
gengtype-lex.c:2544: warning: old-style parameter declaration
gengtype-lex.c: In function `input':
gengtype-lex.c:2657: warning: old-style parameter declaration
/usr/share/bison/bison.simple: In function `yyparse':
/usr/share/bison/bison.simple:379: warning: old-style parameter declaration
warning: structure `reg_info_def' used but not defined
warning: structure `basic_block_def' used but not defined
warning: structure `answer' used but not defined
warning: structure `cpp_macro' used but not defined
warning: structure `reg_info_def' used but not defined
warning: structure `basic_block_def' used but not defined
warning: structure `answer' used but not defined
warning: structure `cpp_macro' used but not defined
insn-conditions.c:739: warning: string length `534' is greater than the length `509' ISO C89 compilers are required to support
insn-conditions.c:1025: warning: string length `533' is greater than the length `509' ISO C89 compilers are required to support
insn-conditions.c:1565: warning: string length `597' is greater than the length `509' ISO C89 compilers are required to support
/usr/share/bison/bison.simple: In function `yyparse':
/usr/share/bison/bison.simple:379: warning: old-style parameter declaration
/usr/share/bison/bison.simple:923: warning: label `yyoverflowlab' defined but not used
Automaton `pentium'
48 NDFA states, 138 NDFA arcs
48 DFA states, 138 DFA arcs
20 minimal DFA states, 82 minimal DFA arcs
158 all insns 17 insn equivalence classes
88 transition comb vector els, 340 trans table els: use comb vect
88 state alts comb vector els, 340 state alts table els: use comb vect
340 min delay table els, compression factor 2
Automaton `pentium_fpu'
80 NDFA states, 172 NDFA arcs
80 DFA states, 172 DFA arcs
75 minimal DFA states, 162 minimal DFA arcs
158 all insns 8 insn equivalence classes
164 transition comb vector els, 600 trans table els: use comb vect
164 state alts comb vector els, 600 state alts table els: use comb vect
600 min delay table els, compression factor 1
Automaton `athlon'
518 NDFA states, 1668 NDFA arcs
518 DFA states, 1668 DFA arcs
76 minimal DFA states, 328 minimal DFA arcs
158 all insns 10 insn equivalence classes
359 transition comb vector els, 760 trans table els: use simple vect
359 state alts comb vector els, 760 state alts table els: use simple vect
760 min delay table els, compression factor 2
Automaton `athlon_load'
162 NDFA states, 855 NDFA arcs
162 DFA states, 855 DFA arcs
162 minimal DFA states, 855 minimal DFA arcs
158 all insns 10 insn equivalence classes
1047 transition comb vector els, 1620 trans table els: use simple vect
1047 state alts comb vector els, 1620 state alts table els: use simple vect
1620 min delay table els, compression factor 2
Automaton `athlon_mult'
16 NDFA states, 48 NDFA arcs
16 DFA states, 48 DFA arcs
16 minimal DFA states, 48 minimal DFA arcs
158 all insns 4 insn equivalence classes
50 transition comb vector els, 64 trans table els: use simple vect
50 state alts comb vector els, 64 state alts table els: use simple vect
64 min delay table els, compression factor 2
Automaton `athlon_fp'
15522 NDFA states, 99908 NDFA arcs
15522 DFA states, 99908 DFA arcs
463 minimal DFA states, 3038 minimal DFA arcs
158 all insns 21 insn equivalence classes
3057 transition comb vector els, 9723 trans table els: use comb vect
3057 state alts comb vector els, 9723 state alts table els: use comb vect
9723 min delay table els, compression factor 1
17012 all allocated states, 101385 all allocated arcs
20258 all allocated alternative states
4765 all transition comb vector els, 13107 all trans table els
4765 all state alts comb vector els, 13107 all state alts table els
13107 all min delay table els
0 locked states num
transformation: 0.012001, building DFA: 7.952498
DFA minimization: 0.468029, making insn equivalence: 0.004000
all automaton generation: 8.528533, output: 0.144009
cc1: out of memory allocating 8579592 bytes after a total of 7716864 bytes
make[2]: *** [insn-attrtab.o] Error 1
make[1]: *** [stageprofile_build] Error 2
make: *** [profiledbootstrap] Error 2
!!! ERROR: sys-devel/gcc-3.4.4-r1 failed.
!!! Function gcc_do_make, Line 1339, Exitcode 2
!!! emake failed with profiledbootstrap
!!! If you need support, post the topmost build error, NOT this status message.
>
>
--
Jorge Almeida
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [gentoo-user] emerge troubles
2006-02-15 1:56 ` Richard Fish
@ 2006-02-15 2:14 ` Jorge Almeida
2006-02-15 2:20 ` Richard Fish
0 siblings, 1 reply; 21+ messages in thread
From: Jorge Almeida @ 2006-02-15 2:14 UTC (permalink / raw
To: gentoo-user
On Tue, 14 Feb 2006, Richard Fish wrote:
> Also, to test whether your system can make large memory allocations, you can do:
>
> python -c "s='x'*(4*(1024*1024))"
> python -c "s='x'*(8*(1024*1024))"
> python -c "s='x'*(16*(1024*1024))"
> python -c "s='x'*(32*(1024*1024))"
> python -c "s='x'*(64*(1024*1024))"
> python -c "s='x'*(128*(1024*1024))"
> python -c "s='x'*(256*(1024*1024))"
>
> The above commands will try to allocate memory from 4M to 256M.
>
> -Richard
>
>
root@jmaa ~ $ python -c "s='x'*(4*(1024*1024))"
~
root@jmaa ~ $ python -c "s='x'*(8*(1024*1024))"
~
root@jmaa ~ $ python -c "s='x'*(16*(1024*1024))"
~
root@jmaa ~ $ python -c "s='x'*(32*(1024*1024))"
~
root@jmaa ~ $ python -c "s='x'*(64*(1024*1024))"
Traceback (most recent call last):
File "<string>", line 1, in ?
MemoryError
~
root@jmaa ~ $ python -c "s='x'*(128*(1024*1024))"
Traceback (most recent call last):
File "<string>", line 1, in ?
MemoryError
~
root@jmaa ~ $ python -c "s='x'*(256*(1024*1024))"
Traceback (most recent call last):
File "<string>", line 1, in ?
MemoryError
<SIGH>
Thanks,
Jorge
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [gentoo-user] emerge troubles
2006-02-15 2:14 ` Jorge Almeida
@ 2006-02-15 2:20 ` Richard Fish
2006-02-15 2:21 ` Richard Fish
2006-02-15 2:24 ` Jorge Almeida
0 siblings, 2 replies; 21+ messages in thread
From: Richard Fish @ 2006-02-15 2:20 UTC (permalink / raw
To: gentoo-user
On 2/14/06, Jorge Almeida <jalmeida@math.ist.utl.pt> wrote:
> root@jmaa ~ $ python -c "s='x'*(4*(1024*1024))"
> ~
> root@jmaa ~ $ python -c "s='x'*(8*(1024*1024))"
> ~
> root@jmaa ~ $ python -c "s='x'*(16*(1024*1024))"
> ~
> root@jmaa ~ $ python -c "s='x'*(32*(1024*1024))"
> ~
> root@jmaa ~ $ python -c "s='x'*(64*(1024*1024))"
> Traceback (most recent call last):
> File "<string>", line 1, in ?
> MemoryError
Any chance this is a resource limit issue?
ulimit -l -m
-Richard
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [gentoo-user] emerge troubles
2006-02-15 2:20 ` Richard Fish
@ 2006-02-15 2:21 ` Richard Fish
2006-02-15 2:25 ` Jorge Almeida
2006-02-15 2:24 ` Jorge Almeida
1 sibling, 1 reply; 21+ messages in thread
From: Richard Fish @ 2006-02-15 2:21 UTC (permalink / raw
To: gentoo-user
On 2/14/06, Richard Fish <bigfish@asmallpond.org> wrote:
> ulimit -l -m
Or better: ulimit -a
-Richard
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [gentoo-user] emerge troubles
2006-02-15 2:20 ` Richard Fish
2006-02-15 2:21 ` Richard Fish
@ 2006-02-15 2:24 ` Jorge Almeida
1 sibling, 0 replies; 21+ messages in thread
From: Jorge Almeida @ 2006-02-15 2:24 UTC (permalink / raw
To: gentoo-user
On Tue, 14 Feb 2006, Richard Fish wrote:
> Any chance this is a resource limit issue?
>
> ulimit -l -m
>
Nope...
$ ulimit -l -m
max locked memory (kbytes, -l) 32
max memory size (kbytes, -m) unlimited
Jorge
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [gentoo-user] emerge troubles
2006-02-15 2:21 ` Richard Fish
@ 2006-02-15 2:25 ` Jorge Almeida
2006-02-15 2:48 ` Richard Fish
0 siblings, 1 reply; 21+ messages in thread
From: Jorge Almeida @ 2006-02-15 2:25 UTC (permalink / raw
To: gentoo-user
On Tue, 14 Feb 2006, Richard Fish wrote:
> Or better: ulimit -a
$ ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) 58593
file size (blocks, -f) unlimited
pending signals (-i) 8191
max locked memory (kbytes, -l) 32
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
stack size (kbytes, -s) 58593
cpu time (seconds, -t) unlimited
max user processes (-u) 8191
virtual memory (kbytes, -v) 58593
file locks (-x) unlimited
>
Jorge
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [gentoo-user] emerge troubles
2006-02-15 2:25 ` Jorge Almeida
@ 2006-02-15 2:48 ` Richard Fish
2006-02-15 3:14 ` Jorge Almeida
0 siblings, 1 reply; 21+ messages in thread
From: Richard Fish @ 2006-02-15 2:48 UTC (permalink / raw
To: gentoo-user
On 2/14/06, Jorge Almeida <jalmeida@math.ist.utl.pt> wrote:
> On Tue, 14 Feb 2006, Richard Fish wrote:
> data seg size (kbytes, -d) 58593
> virtual memory (kbytes, -v) 58593
These are preventing any process spawned by this user from allocating
more than 58593 bytes of memory (which is why 32M works, and 64M
fails)
Try:
ulimit -d unlimited
ulimit -v unlimited
-Richard
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [gentoo-user] emerge troubles
2006-02-15 2:48 ` Richard Fish
@ 2006-02-15 3:14 ` Jorge Almeida
2006-02-15 15:24 ` Zac Slade
0 siblings, 1 reply; 21+ messages in thread
From: Jorge Almeida @ 2006-02-15 3:14 UTC (permalink / raw
To: gentoo-user
On Tue, 14 Feb 2006, Richard Fish wrote:
> On 2/14/06, Jorge Almeida <jalmeida@math.ist.utl.pt> wrote:
>> On Tue, 14 Feb 2006, Richard Fish wrote:
>> data seg size (kbytes, -d) 58593
>> virtual memory (kbytes, -v) 58593
>
> These are preventing any process spawned by this user from allocating
> more than 58593 bytes of memory (which is why 32M works, and 64M
> fails)
>
> Try:
> ulimit -d unlimited
> ulimit -v unlimited
>
> -Richard
>
>
Well, so that was it! I just finished compiling gcc.
I wonder why those limits were set for user root?!
My home computer didn't have such restriction, and I recently made a new
install on the computer that had all this problem, so I'm sure I didn't
do it myself and forgot it...
It's a relief to know it's not hw problem!
Thank you, and thanks also to Benno and Zac.
Jorge
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [gentoo-user] emerge troubles
2006-02-15 3:14 ` Jorge Almeida
@ 2006-02-15 15:24 ` Zac Slade
2006-02-15 15:37 ` Jorge Almeida
0 siblings, 1 reply; 21+ messages in thread
From: Zac Slade @ 2006-02-15 15:24 UTC (permalink / raw
To: gentoo-user
On Tuesday 14 February 2006 21:14, Jorge Almeida wrote:
> Well, so that was it! I just finished compiling gcc.
> I wonder why those limits were set for user root?!
> My home computer didn't have such restriction, and I recently made a new
> install on the computer that had all this problem, so I'm sure I didn't
> do it myself and forgot it...
Check /etc/limits to see what the defaults are. I'd also look at any shell
scripts that are being sourced during login (/etc/profile ~/.bashrc, etc.).
> It's a relief to know it's not hw problem!
Memory allocation is one of those things that usually isn't. Normally you'd
see physical memory errors as programs randomly crashing (like the kernel,
with no PANIC). You also might notice when you start the system up that it
is reporting less memory than you have installed.
> Thank you, and thanks also to Benno and Zac.
Very appreciated.
--
Zac Slade
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [gentoo-user] emerge troubles
2006-02-15 15:24 ` Zac Slade
@ 2006-02-15 15:37 ` Jorge Almeida
0 siblings, 0 replies; 21+ messages in thread
From: Jorge Almeida @ 2006-02-15 15:37 UTC (permalink / raw
To: gentoo-user
On Wed, 15 Feb 2006, Zac Slade wrote:
> Check /etc/limits to see what the defaults are. I'd also look at any shell
> scripts that are being sourced during login (/etc/profile ~/.bashrc, etc.).
>
/etc/limits is completely commented out. Couldn't find anything in
/etc/profile nor in /etc/bashrc. And ~/.bashrc only has what I put there
after Richard's reply.
Cheers.
Jorge Almeida
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 21+ messages in thread
end of thread, other threads:[~2006-02-15 15:44 UTC | newest]
Thread overview: 21+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-02-14 10:38 [gentoo-user] emerge troubles Jorge Almeida
2006-02-14 14:50 ` Benno Schulenberg
2006-02-14 18:12 ` Jorge Almeida
2006-02-14 20:43 ` Benno Schulenberg
2006-02-14 21:10 ` Jorge Almeida
2006-02-14 23:43 ` Benno Schulenberg
2006-02-14 23:57 ` Zac Slade
2006-02-15 1:25 ` Jorge Almeida
2006-02-15 1:45 ` Zac Slade
2006-02-15 1:56 ` Richard Fish
2006-02-15 2:14 ` Jorge Almeida
2006-02-15 2:20 ` Richard Fish
2006-02-15 2:21 ` Richard Fish
2006-02-15 2:25 ` Jorge Almeida
2006-02-15 2:48 ` Richard Fish
2006-02-15 3:14 ` Jorge Almeida
2006-02-15 15:24 ` Zac Slade
2006-02-15 15:37 ` Jorge Almeida
2006-02-15 2:24 ` Jorge Almeida
2006-02-15 2:10 ` Jorge Almeida
2006-02-15 1:51 ` Richard Fish
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox