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] memtest86+: Hardlocks on systems with more than 4GB of RAM (packaging/compilation issue, upstream build works fine)
Date: Fri, 15 Apr 2022 17:03:49 +0200	[thread overview]
Message-ID: <20220415150349.2-OjcyF9Eq3RZmu30UCpeE-Podq64NVb4TYoz3Ho_K0@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: 2017 bytes --]

Closed issue by Veyrdite on void-packages repository

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

Description:
### System
Systems tried:

* Gigabyte P67A-UD3R-B3 + i5-3470S 
* HP Elite 8200 + i5-2500

DDR3 modules used in tests:

* 2x2GB 1600 Ripjaws
* 2x2GB 1333 Microns
* 2x4GB 1333 Samsung
* 1x2GB 1333 Kingston

xuname from one system used: Void 4.19.42_1 x86_64 GenuineIntel notuptodate FFFFFFFFFFF (probably not relevant, kernel is not loaded when bug occurs)

package version: memtest86+-5.01_5

### Behaviour

Memtest86+ 5.01 from the official memtest86+ website: works fine
Memtest86 4.3.7 from the official memtest86 website: works fine
**Memtest86+ 5.01 from the void repos: freezes during the first test if more than 4GB of DIMMs are installed.**

This arbitrary % is completely repeatable and depends on the order + sizes of the DIMMs installed.

Only tested on Sandy and Ivy bridge DDR3 motherboards (see motherboards + processors at top of this report).

### Steps to reproduce the behavior

1. xbps-install memtest86+
2. Boot into it using either grub2 or syslinux (both have been tested)
3. Wait for the % of the very first test to progress until full CPU lockup (usually takes <5 seconds)

(note that the '+' still blinking on the screen is a red herring, this is a 'flashing text' non-OS (GPU?) feature, not an indicator of activity in the test)

To test the official version of memtest86+: download it to your /boot directory and modify your grub/syslinux config to list it.  Don't try and use the pre-made ISOs or bootable USBs, they have really poor system compatibility.

To test the official version of memtest86: its USB-bootable versions have very good compatibility, use them.

### Misc context

Void compiles memtest86+ from source, somewhere in this process the bug is being created or uncovered.  Compare the binaries:
```
179K /boot/memtest86+    (from void repos)
147K /boot/officialmemtest.bin  (from memtest86+ website)
```

      parent reply	other threads:[~2022-04-15 15: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
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 ` 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=20220415150349.2-OjcyF9Eq3RZmu30UCpeE-Podq64NVb4TYoz3Ho_K0@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).