physical address ranges when limited with mem=xxx

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello

I found a bad bit in my RAM with memtest86 somewhere after 120M on a 128M
module. So, if I pass a parameter like mem=(total-4M) to the kernel, will
exactly those last 4M of RAM not be used, or is not guaranteed?
Intuitively, the answer should be "yes". Yes, that board is the last of
the 2, at least as reported by memtest - it reports address a bit above
380M. BTW, the error I see appears only at one bit and only when tested
with one pattern, and not every pass... How bad is this actually?

Thanks
Guennadi
---------------------------------
Guennadi Liakhovetski, Ph.D.
DSA Daten- und Systemtechnik GmbH
Pascalstr. 28
D-52076 Aachen
Germany


--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
FAQ:           http://kernelnewbies.org/faq/


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux