From: "Ludovic Courtès" <ludo@gnu.org>
To: Mayeul Cantan <oss+guix@mayeul.net>
Cc: 41362@debbugs.gnu.org
Subject: bug#41362: error when running guix pull on i686-linux
Date: Fri, 24 Jul 2020 15:06:46 +0200 [thread overview]
Message-ID: <87a6zp9i55.fsf@gnu.org> (raw)
In-Reply-To: <98ab03d7-c172-03bb-481e-0021f3af30fe@cantan.eu> (Mayeul Cantan's message of "Thu, 23 Jul 2020 14:25:39 +0200")
Hello,
Mayeul Cantan <oss+guix@mayeul.net> skribis:
> Thanks to your comment regarding a possible memory corruption issue, I
> ran my memory module trough memtest86+, which identified several
> problematic addresses. So this was likely a hardware issue.
>
> I tried blacklisting them with the memmap kernel command-line option,
> but that didn't fix the issue. Looking at the addresses, I reduced my
> memory to 600 MiBs (mem=600M, which seems to solve the issue, though
> it makes `guix pull` extremely slow.
>
> I haven't touched that system in a while, so my recollection is a bit
> fuzzy. I am going to try again, though. (I would have loved to
> experiment on another computer on top of another distro, but wasn't
> ready to give guix root access back then).
>
> I think this really was a HW issue, but I will keep you posted.
It does look like a hardware issue from what you describe.
Thanks for the update,
Ludo’.
prev parent reply other threads:[~2020-07-24 13:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-17 13:16 bug#41362: error when running guix pull on i686-linux Mayeul Cantan
2020-05-29 16:02 ` Ludovic Courtès
2020-07-22 20:28 ` Ludovic Courtès
2020-07-23 12:25 ` Mayeul Cantan
2020-07-24 13:06 ` Ludovic Courtès [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
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=87a6zp9i55.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=41362@debbugs.gnu.org \
--cc=oss+guix@mayeul.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).