lkml.org 
[lkml]   [2012]   [Apr]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    SubjectRe: [PATCH resend v3] x86: memtest: WARN if bad RAM found
    From
    On Mon, Apr 23, 2012 at 1:28 PM, Jonathan Nieder <jrnieder@gmail.com> wrote:
    > Yinghai Lu wrote:
    >> On Mon, Apr 23, 2012 at 11:26 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:
    >
    >>> --- a/arch/x86/mm/memtest.c
    >>> +++ b/arch/x86/mm/memtest.c
    >>> @@ -30,6 +30,8 @@ static u64 patterns[] __initdata = {
    >>>
    >>>  static void __init reserve_bad_mem(u64 pattern, u64 start_bad, u64 end_bad)
    >>>  {
    >>> +       WARN_ONCE(1, "Bad RAM detected. Use memtest86+ to perform a thorough test\n"
    >>> +                 "and the memmap= parameter to reserve the bad areas.");
    >>
    >> You must be kidding : calling memtest86+ "thorough test".
    >
    > How about "more thorough test"?  Or do you have a better
    > recommendation for users?

    The reason for adding early_memtest is for debug purpose.
    Sometimes BIOS mess up setting, on some booting memory is ok, but
    other booting the memory is not initialized properly.

    in that case: preboot memtest tools is not going to help.

    also preboot memtest tools and early_memtest is not stressed enough.
    --- only one process is running.
    Need to run memtester multiple instances to test your memory and systems.

    Yinghai
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2012-04-24 00:15    [W:0.027 / U:0.896 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site