From: yopito <yopito@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: memtest86+: Hardlocks on systems with more than 4GB of RAM (packaging/compilation issue, upstream build works fine)
Date: Sat, 14 Aug 2021 12:03:32 +0200 [thread overview]
Message-ID: <20210814100332.gVC2kNfuVyBO0bbjNotB2FQt90lYvnp75pMXusO183c@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11691@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 679 bytes --]
New comment by yopito on void-packages repository
https://github.com/void-linux/void-packages/issues/11691#issuecomment-898874065
Comment:
thanks for this detailed report.
I can't give a try to memtest 5.01 since musl libc on my system.
however, my WIP memtest 5.31b Void package is still working fine, I've just restested it (see https://github.com/void-linux/void-packages/pull/21179)
Would you mind give a try ?
This means building this package by yourself from source using branch https://github.com/yopito/void-packages/tree/memtest.5.31b .
I also might crossbuild this package for you (either glibc or musl) and provide it to you prefer (unofficial package ATM).
next prev parent reply other threads:[~2021-08-14 10:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11691@inbox.vuxu.org>
2021-08-11 0:25 ` Veyrdite
2021-08-11 2:07 ` Frosty-J
2021-08-14 10:03 ` yopito [this message]
2021-08-17 9:18 ` Veyrdite
2021-08-17 9:18 ` Veyrdite
2021-08-18 11:42 ` leahneukirchen
2021-08-18 11:46 ` leahneukirchen
2021-08-18 14:24 ` leahneukirchen
2021-08-21 15:42 ` yopito
2021-08-21 16:35 ` yopito
2022-04-15 2:12 ` github-actions
2022-04-15 15:03 ` [ISSUE] [CLOSED] " leahneukirchen
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=20210814100332.gVC2kNfuVyBO0bbjNotB2FQt90lYvnp75pMXusO183c@z \
--to=yopito@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).