tiomap-dev team mailing list archive
-
tiomap-dev team
-
Mailing list archive
-
Message #00532
[Bug 690370] Re: Strange out of memory on pandaboard
Hi Marcin Juszkiewiczm,
You mean that you are building the kernel on the filesystem over usb storage, and at the same time
you are controlling from remote, then oom happened?
If so, could you disconnect ethernet connection(usbnet) to build kernel on usb storage and
see if the oom can happen?
thanks,
--
You received this bug notification because you are a member of TI OMAP
Developers, which is a direct subscriber.
https://bugs.launchpad.net/bugs/690370
Title:
Strange out of memory on pandaboard
Status in “linux-ti-omap4” package in Ubuntu:
New
Bug description:
A GCC trunk bootstrap fails with:
gcc -g -fkeep-inline-functions -DIN_GCC -W -Wall -Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition -Wc++-compat -fno-common -DHAVE_CONFIG_H -DGENERATOR_FILE -o build/gengtype \
build/gengtype.o build/errors.o build/gengtype-lex.o build/gengtype-parse.o build/gengtype-state.o build/version.o ../build-armv7l-unknown-linux-gnueabi/libiberty/libiberty.a
/bin/bash ../../trunk/gcc/../move-if-change tmp-gi.list gtyp-input.list
echo timestamp > s-gtyp-input
build/gengtype \
-S ../../trunk/gcc -I gtyp-input.list -w gtype.state
build/gengtype \
-r gtype.state
out of memory allocating 4072 bytes after a total of 199240912 bytes
make[3]: *** [s-gtype] Error 1
make[3]: Leaving directory `/home/guerby/build/gcc'
make[2]: *** [all-stage1-gcc] Error 2
make[2]: Leaving directory `/home/guerby/build'
make[1]: *** [stage1-bubble] Error 2
make[1]: Leaving directory `/home/guerby/build'
make: *** [bootstrap] Error 2
real 8m9.482s
user 4m0.680s
sys 1m37.547s
Looking at top at the time of failure:
Mem: 681844k total, 368152k used, 313692k free, 6076k buffers
Swap: 0k total, 0k used, 0k free, 240456k cached
/home is mounted over NFS, swap is commented out, make bootstrap after
a clean boot, /etc/rc.local has:
sysctl -w vm.overcommit_memory=2
echo 0 > /proc/sys/kernel/randomize_va_space
In a different situation, with mem=768M in a previous test I got various issues reported in /var/log/messages
copy here: wget http://guerby.org/ftp/messages-pandaboard
rsalveti asked me to open a report.