>
> I decided that my 486 was too slow for C++ development, so went out and
> bought a P5-133 system with a Triton chipset PCI motherboard last weekend...
>
> Both 1.2.11 and 1.2.13 exhibited a horrible corrupting problem where I
> would work for a while, then gcc would spew some internal error before
> taking out virtual memory and, after enough restarts, my root
> filesystem.
Did you also buy new and faster RAM? I suspect your RAM is too slow!
>
> So I tried several of the more recent 1.3.* series, which mention
> corrupting PCI chipset fixes in the 'config' process. I haven't seen the
> corrupting problem, but now emacs bombs in its memory manager (xemacs
> works ok) and 'ps u' and 'top' both die with a floating exception:
>
> > ps u
> USER PID %CPU %MEM SIZE RSS TTY STAT START TIME COMMAND
> Floating exception
You haven't been following the list, did you? You need to upgrade
your ps and top (get procps-0.99) or see your Linux representative (=
read FAQs)
>
> I'm hoping this is a telling symptom of a larger problem that makes the
> majordomo 'perl' scripts consume all of the memory on my system.
>
> Has anyone else seem this problem? When were the chipset fixes
> introduced into a kernel release? I can drop back to that version to see
> if it fixes the problem(s).
>
> -dave