Hi! On Tue, 29 May 2012 21:25:34 +0200, I wrote: > Just a quick report regarding recovering from memory pressure. This is > with gnumach-image-1.3.99-486-dbg 2:1.3.99.dfsg.git20120219-1.
OK, there seems to be one pattern here, but it's simply resource exhaustion, I assume. > During GCC testing, my system collapsed. Unfortunately, there was no > farewell note found. Re-running the offending (I suppose) test manually, > »[...]master.build/gcc/xgcc -B[...]/master.build/gcc/ > -fno-diagnostics-show-caret -O2 -w -c -o limits-structnest.o > [...]/master/gcc/testsuite/gcc.c-torture/compile/limits-structnest.c«, I > see that it within its few seconds of run time it nearly completely sucks > up of what vmstat reports as free memory. (Running it manually now, > there is no system crash, unfortunately (?).) This crash (when testing gcc.c-torture/compile/limits-structnest.c directly after a GCC build without an intermediate reboot) happened again. Thus, it is advisable to reboot after having built and installed GCC, before running the testsuite, as otherwise there seems to be a tendency that the system crashes during the gcc.c-torture/compile/limits-structnest.c tests, which are rather memory hungry. Probably there is already too much memory in use for other purposes (ext2fs page cache, for example), and this test's requirements cannot be satisfied by Mach, and the system gets into an instable state, <http://www.gnu.org/software/hurd/open_issues/ext2fs_page_cache_swapping_leak.html>. It also seems advisable to add another reboot before running check-target, that is, separate make check's check-host and check-target (see [build]/Makefile:do-check), as otherwise there seems to be a tendency for the system crashing sometime after the latter has started. (Running check-host accumulates to something like 44 hours worth of forking/execing of GCC and testcases.) Grüße, Thomas
pgpVbKzA5wj7i.pgp
Description: PGP signature
