From: Nick Warne <nick@linicks.net>
To: linux-kernel@vger.kernel.org
Subject: Question: kernel->memtest documentation
Date: Sat, 21 Feb 2015 20:23:29 +0000 [thread overview]
Message-ID: <54E8E941.6030009@linicks.net> (raw)
Hi all,
I have had an issue on my server for a few months with random shutdowns.
Today I configured the kernel option 'memtest' (on 3.19) and it appears
to work when I reading boot logs... but trying to research on what it
does is non-existent.
Reading the code there appears to be no log if bad memory is found (or
not, I dunno?).
Would I see anything in particular in logs if memtest does find something?
Is there a way to see if memory is mapped out to not use?
This appears to be a great option, but nothing on it's usage.
Maybe I am an idiot...
Thanks,
Nick
--
Gosh that takes me back... or is it forward? That's the trouble with
time travel, you never can tell."
-- Doctor Who "Androids of Tara"
reply other threads:[~2015-02-21 20:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54E8E941.6030009@linicks.net \
--to=nick@linicks.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.