Since about two weeks ago, when compiling some app from source, I would sometimes run into problems with GCC failing to compile, but not because of the source code or dependencies, GCC itself would error out with a segmentation fault:
Internal compiler error: Segmentation fault (..etc, please repost this, etc...)
Then last friday, makepkg would also error out while making a package, with a segmentation fault.
Yesterday morning it took 4 attempts to build a custom kernel (with the -ck patchset), and later on in the day I wasn't even able to get fluxbox to compile.
Finaly today, none of the partitions where I had VL installed would boot properly, the kernel would panic and spit out tons of trace-back code. The few times I was able to login, it would simply freeze up at random...so then I'de finaly had enough.
The most logical seemed to be the memory, so I grabbed a bootable memtest86
iso, burned it on my laptop and booted my PC with it.
And after only few seconds memtest started listing bad addresses non-stop....http://clientes.netvisao.pt/alynnsut/memtest_results.JPG
So its been at this for almost 4 hours now, and it pretty much looks like the second half of my 256mb of ram are completely buggered.
Its kind of strange that over the last two weeks its like that memory module has been "decaying" little by little, instead of dying a "sudden death" like most hardware does...
What could have caused this to happen?
There haven't been any blackouts or power surges here for quite a long time (at least 8 months), and that is normally the kind of thing that blasts my hardware to the next life...
(Thank goodness for my trusty laptop, also running VL