> System stats:
> k6-2-332.5, 128m ram, 256 swap, 2.1.105.
>
> I did a 'time make -j zImage modules' on 2.1.131ac4 to test my system out
> today, and relatively early random gcc's, cpp's, and make's started dying. No
> other program anywhere was killed, only the ones involved in this compile run.
> What was odd, was that the top level make was killed, so the other makes kept
> running in the background. a killall make helped that on another console, but
> shouldn't the kernel kill child processes first, before parents in low-mem
> situations? or at least make it a sysctl option.
Are you using egcs? On a Cyrix P150+ box here it is unusable, segfaults,
SIGILL, SIGSEGV, you name it! I've noticed this from time to time over
the past few egcs revisions; they seem to antagonize some bug in the Cyrix
microcode. If I switch to gcc-2.7.2 it works fine.
On my dual PPro SMP machine, the same egcs executables are flawless. I've
seen other reports of this Cyrix strangeness, and wonder if you aren't
seeing something like it, but with AMD flavoring.
Steve
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/