You bet it can. Memory right now is sooooo bad that "hardware" type memory checkers can't even find the problems with the SIMMS. So the best way to check for memory problems, if you have been listening to this list-server is to compile a kernel an see if you machine takes a dump. Apparantly, the stress of doing this process causes sever enough strain to exercise the componets to their utmost. I just received a new Micron Server, cost $10,000 and after beating ourselves silly over the weekend trying to get it to copy files from the old Novell server to the new Micron server. The file copy process was failing over a period of time as stuff became stuck in memory. We decided to start swaping SIMM placement, and sure enough the Micron TSE agreed we had bad memory. The system boot fine no errors POSTing, or loading the OS or even running in an idle state. Good Luck with your situtation. -ted Arun K. Khan wrote:
I moved a 32MB 168 SDRAM from another machine to my SuSE 5.1 machine.
POST reports that everything is OK with the Memory with each Power ON or C-A-D.
Since putting this DIMM I have experienced random 'segmentation fault' and 'core dump' two times today. First time it was during shutdown of routing whilst shutting down and the second time it was from SMB servers whilst booting up. The 'seg. fault' did not lock up the machine and in each instance the subsequent shutdown/boot up processes completed successfully. On subsequent shutdown and reboot things were OK.
Interestingly enough, when I had this DIMM in a Win95 machine it would cause random lock up of the machine and I would have to reset the machine.
Can a memory chip be flaky, yet pass POST tests and subsequently be the cause for segmentation fault? Is there any way to test out the DIMM besides the POST?
Any comments from those who have experienced similar symptoms?
TIA -- Arun Khan - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
-- Ted Maciag - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e