4
#<Comment:0x2ac500fdd2f8>#<Comment:0x2ac500fdc650>#<Comment:0x2ac500fdc4e8>
<p>This trick is based upon the work of Rick van Rein (<a href="http://rick.vanrein.org/linux/badram/index.html">Rick’s Homepage</a> )an many others. They developed a patch which allows you to mark bad ram pages. As I am curious I did’nt want to wait for a new version of the patch, fitting the 2.6.25 kernel. So I modified the patch to work with the current kernel.</p>
<h1>Prerequisites</h1>
<p>Memtest86+ (to find out which pages are bad)</p>
<p>Kernel sources for the 2.6.25 kernel (i.e. at kernel.org or your distri)</p>
<p>The patch attached to that trick</p>
<h1>What to do</h1>
Start your machine and run memtest with the BadRam error reporting option.
This may result in an output like
<pre>
<code>
badram=0x09ada0b8, 0xfffffffc
</code>
</pre>
This option can directly appended to your boot entry in /boot/grub/menu.lst
Get the patch an install it via
<pre>
<code>
patch -p1 < BadRam-2.6.25.1.patch
</code>
</pre>
in your kernel source directory. Compile your patched kernel an reboot it with the badram option appended. Voila no more crashes caused by allocation of faulty ram…
You may want to look up
<pre>
<code>
dmesg|grep Memory
</code>
</pre>
to see which pages are marked bad.
Textile
This trick is based upon the work of Rick van Rein ("Rick's Homepage":http://rick.vanrein.org/linux/badram/index.html )an many others. They developed a patch which allows you to mark bad ram pages. As I am curious I did'nt want to wait for a new version of the patch, fitting the 2.6.25 kernel. So I modified the patch to work with the current kernel.
#Prerequisites
Memtest86+ (to find out which pages are bad)
Kernel sources for the 2.6.25 kernel (i.e. at kernel.org or your distri)
The patch attached to that trick
#What to do
Start your machine and run memtest with the BadRam error reporting option.
This may result in an output like
<pre>
<code>
badram=0x09ada0b8, 0xfffffffc
</code>
</pre>
This option can directly appended to your boot entry in /boot/grub/menu.lst
Get the patch an install it via
<pre>
<code>
patch -p1 < BadRam-2.6.25.1.patch
</code>
</pre>
in your kernel source directory. Compile your patched kernel an reboot it with the badram option appended. Voila no more crashes caused by allocation of faulty ram...
You may want to look up
<pre>
<code>
dmesg|grep Memory
</code>
</pre>
to see which pages are marked bad.
2008-04-29T10:12:12+02:00
22
/var/rails/howflow/public/trick/file/106/BadRAM-2.6.25.1.patch.txt
106
en
0
7
avoid_allocation_of_bad_ram_blocks
2008-04-29T08:28:32+02:00
published
Recently I had problems with a bad ram module. This trick allows you to mark blocks as bad, so they are never used and you dont't have to deposit your memory in the trash, just because a few kb are faulty.
Avoid allocation of bad ram blocks
2008-05-23T18:05:26+02:00
37