Можно и куда-то сюда посмотреть:
kernel-parameters.txt
memory_corruption_check=0/1 [X86]
Some BIOSes seem to corrupt the first 64k of
memory when doing things like suspend/resume.
Setting this option will scan the memory
looking for corruption. Enabling this will
both detect corruption and prevent the kernel
from using the memory being corrupted.
However, its intended as a diagnostic tool; if
repeatable BIOS-originated corruption always
affects the same memory, you can use memmap=
to prevent the kernel from using that memory.
memory_corruption_check_size=size [X86]
By default it checks for corruption in the low
64k, making this memory unavailable for normal
use. Use this parameter to scan for
corruption in more or less memory.
memory_corruption_check_period=seconds [X86]
By default it checks for corruption every 60
seconds. Use this parameter to check at some
other rate. 0 disables periodic checking.
memtest= [KNL,X86,ARM] Enable memtest
Format: <integer>
default : 0 <disable>
Specifies the number of memtest passes to be
performed. Each pass selects another test
pattern from a given set of patterns. Memtest
fills the memory with this pattern, validates
memory contents and reserves bad memory
regions that are detected.
Моё видение в этом плане:
Бесследно такие фокусы с проверкой больших массивов памяти не пролазят. Любое пожелание запуска кода, это занятые ресурсы. Есть разница между проверкой 64 кило и двух сотен метров.
Говорят возможно при наличии патча BadRAM:
https://help.ubuntu.com/community/BadRAMТ.е. после накладывания патча, парень исключил использование памяти в диапазоне адресов передачей параметра загрузчику:
GRUB_BADRAM = "0x7DDF0000,0xffffc000"
