This is generally a Hardware fault.
Segmentation faults can be caused by a number of things being;./module_load: line 39: 464 Segmentation fault /sbin/insmod -f $MOD
If you've transfered a program from some other machine, you may have corrupted the file in the transfer.
Compiling a Linux kernel.
The machine has been running for years and suddenly stuff like this starts happening. This is called kernel panic.
My hunch points to Kernel Panic.
Possible reasons for a system panic, is an E Trap. Basically, an E trap is a page fault that referenced an impossible page: the CPU tries to access an address that does not exist and can't be accessed. As page references are normally very carefully managed, the usual cause for this is bad (defective) RAM; scrambled bits point the CPU toward disaster and it blindly follows.
Therefore, if you have a kernel panic on a machine that otherwise has been running along for months or years, bad RAM is the most likely suspect.
Bookmarks