This is my first post in these forums. I'm still quite new to Linux (using Mint 9) so please bear with my not-very-articulate question(s) ...
When I boot up and open up a tty terminal I get a message saying "Memory corruption detected in low memory." I've done an extensive google search about the issue and it seems not uncommon. I ran a memtest with no errors returned, so I'm sure that there's nothing really wrong with the memory; apparently it's a bug in the kernel that's causing this.
I came across this message in the Arch Linux forum about this very issue:
Fancy thing this "Corrupted Low Memory", as I get it as well on my T42...
I downgraded to kernel 220.127.116.11 and still had the Corrupt message in my dmesg. I then downgraded to 18.104.22.168 and voila the Corrupt messages went away, and so did the random module crashes (as you seem to be getting too after the Corrupt messages).
The problem seems to be with:
CONFIG_X86_CHECK_BIOS_CORRUPTION: Check for low memory corruption
Which is a new feature ever since 2.6.28.x kernel. It was working properly for us T42 ppl, until 2.6.30.x came along, and still hasn't been fixed in 2.6.31.x. To fix this and get system stability back, add the following to the end of your kernel line (in either Lilo or Grub):
That stops the kernel from checking for corrupted low memory, but, since the check procedure messes up the system and causes modules to crash, it's better to disable it until the problem is worked out.
To be on the safe side, I ran a few memory check programs, and they all ran without errors. So my low memory isn't corrupt after all, just a bug in a feature that can be disabled.
This seems a promising way to deal with this false flag, but I just don't know what file this person is referring to that needs to be edited. Can anyone tell me where the "kernel line" is? Thanks very much in advance.