unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: help-guix@gnu.org
Subject: Re: Frequent git repository corruptions
Date: Sun, 30 Sep 2018 15:07:19 -0400	[thread overview]
Message-ID: <87muryby8o.fsf@netris.org> (raw)
In-Reply-To: <87bm8fcffm.fsf@tobias.gr> (Tobias Geerinckx-Rice's message of "Sun, 30 Sep 2018 14:55:57 +0200")

Tobias Geerinckx-Rice <me@tobias.gr> writes:

> Tobias Geerinckx-Rice wrote:
>> Pierre Neidhardt wrote:
>>> Yup, that's what I've found out as well.
>>>
>>> There is an AUR package for memtest86 (no +) on EFI:
>>>
>>> 	https://aur.archlinux.org/packages/memtest86-efi/
>
> I stand by my initial pronouncement:
>
>> Say no more :-) That is proprietary software.
>
> Only the old, unmaintained (and notably non-UEFI) version 4 is
> GPL2. Newer versions are mystery meat.[1]

Oh, that's unfortunate :-(

Does anyone know of free software that can test all of the RAM in a
machine and that runs on systems with UEFI?

Failing that, there's 'memtester' which runs as a normal program under
Linux (the kernel).  This method is unable to test RAM that's allocated
to the kernel or to other processes, but if you stop as many services as
possible and run it from a text terminal, it should be able to test most
of the RAM.

We don't yet have 'memtester' in Guix, but it looks like it should be
easy to package.

      Mark

  reply	other threads:[~2018-09-30 19:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-26 10:03 Frequent git repository corruptions Pierre Neidhardt
2018-09-26 10:50 ` Ricardo Wurmus
2018-09-26 11:43   ` Pierre Neidhardt
2018-09-27  8:03 ` Mark H Weaver
2018-09-27  8:10   ` Pierre Neidhardt
2018-09-28 13:16     ` Pierre Neidhardt
2018-09-28 13:31       ` Tobias Geerinckx-Rice
2018-09-28 14:18         ` Pierre Neidhardt
2018-09-29 12:50           ` Pierre Neidhardt
2018-09-29 19:08             ` Björn Höfling
2018-09-30 12:33               ` Pierre Neidhardt
2018-09-30 12:39                 ` Tobias Geerinckx-Rice
2018-09-30 12:43                   ` Tobias Geerinckx-Rice
2018-09-30 12:55                     ` Tobias Geerinckx-Rice
2018-09-30 19:07                       ` Mark H Weaver [this message]
2018-09-30 19:22                         ` Tobias Geerinckx-Rice
2018-09-30 21:27                           ` Mark H Weaver
2018-10-13 12:55                             ` Pierre Neidhardt

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87muryby8o.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=help-guix@gnu.org \
    --cc=me@tobias.gr \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).