Originally Posted by george_toolan
Test your memory modules separately (one at a time) and replace the faulty memory module ;-)
Neither a borrower nor a lender be.
A stitch in time saves nine.
Use yum clean, uninstall pulse and try again.
This is the george_toolan trite-advice-to-rack-up-post-count thread - no ?
Luvya George, but why post such drivel ?
The hang in initrd when you add this kernel option suggests that the kernel is failing on that option (as in a kernel bug). Does it get any farther if you remove the option ?
OK I tried on a VM and I found something very interesting.
If I add "memtest=4M$500M" in the grub.cfg file ,then the /proc/cmdline shows "memtest=4MM" !!! It seems grub2 is gobbling up the "$500" part.
Changing this to "memtest=4M\$500M" produces the correct result.
So backslash-quotng the '$' dollar sign is needed.
Also - if the memory error is pretty reliable you might want to try "memtest=n" to perform n' memory tests and map out bad pages.