Github messages for voidlinux
 help / color / mirror / Atom feed
From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] RFC: Linux5.15 - enabling CONFIG_MEMTEST
Date: Tue, 14 Dec 2021 14:13:04 +0100	[thread overview]
Message-ID: <20211214131304.lYxtWvuxY9ef_Od5PwfjVKd_gJZ5f0CUBMC6RXS4Jqc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34399@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 653 bytes --]

Closed issue by daerich on void-packages repository

https://github.com/void-linux/void-packages/issues/34399

Description:
Hi :D,
while looking for a way to, just in case, checking most of the installed memory for corruption/faulty behavior on Linux, I stumbled upon
the "memtest=" kernel parameter, which supposedly lets you run those kinds of tests(in a very primitive way).
Now, not being proficient in all of the Kernels quirks/bugs, is there a reason it is disabled by default in Void's (latest) packaged Kernel(s)?
And, could it be enabled?
Or is the gain miniscule, the feature obscure/deprecated, unreliable, not qualified for normal use?

      parent reply	other threads:[~2021-12-14 13:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-06  1:32 [ISSUE] Question: Linux5.15 - enablling CONFIG_MEMTEST daerich
2021-12-06 15:44 ` parallelistic
2021-12-12 22:02 ` daerich
2021-12-12 22:03 ` daerich
2021-12-12 22:03 ` daerich
2021-12-12 22:12 ` daerich
2021-12-12 22:18 ` Question: Linux5.15 - enabling CONFIG_MEMTEST daerich
2021-12-13 18:42 ` RFC: " leahneukirchen
2021-12-14 13:13 ` leahneukirchen [this message]

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=20211214131304.lYxtWvuxY9ef_Od5PwfjVKd_gJZ5f0CUBMC6RXS4Jqc@z \
    --to=leahneukirchen@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).