On Fri, Oct 12, 2012 at 11:40 AM, Hilton Gibson <[email protected]> wrote: > If it's REAL RAM, then I would suspect faulty RAM. > This can happen. > Reducing the memory need may bypass the faulty RAM.
Indeed, the stackoverflow question I posted mentions checking RAM with memtest86 If you find it's bad, you don't have to toss it, Linux is able to bypass the bad ram (based on location memtest gives you): http://blog.nguyenvq.com/2012/03/30/test-ram-with-memtest86-and-ignore-bad-parts-with-badram-in-grub/ PS. Funny thing, I initially typed "bad rum" instead of "bad ram". Must be my subconscious playing tricks with me: http://www.bbc.co.uk/news/world-europe-19608461 Regards, ~~helix84 ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
