Re: memtest86+: Hardlocks on systems with more than 4GB of RAM (packaging/compilation issue, upstream build works fine)

Re: memtest86+: Hardlocks on systems with more than 4GB of RAM (packaging/compilation issue, upstream build works fine)

[Veyrdite]

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

New comment by Veyrdite on void-packages repository

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

Comment:
I can confirm this bug still occurs for me.

@Frosty-J N.B. memtest.org != memtest86+, different product.

FWIW memtest86+'s "bootable" images never seem to work as well as memtest's unless you put a bootloader (eg grub or syslinux) in front of them.  I've been using the official memtest86+ bin by copying the void-memtest entry in my bootloader config and just editing the filename it points to.

Re: memtest86+: Hardlocks on systems with more than 4GB of RAM (packaging/compilation issue, upstream build works fine)

[Frosty-J]

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

New comment by Frosty-J on void-packages repository

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

Comment:
Isn't the one at memtest.org MemTest86+? It has the same name and version numbers, and is identical in both appearance and function.

Re: memtest86+: Hardlocks on systems with more than 4GB of RAM (packaging/compilation issue, upstream build works fine)

[yopito]

[-- 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).
 

Re: memtest86+: Hardlocks on systems with more than 4GB of RAM (packaging/compilation issue, upstream build works fine)

[Veyrdite]

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

New comment by Veyrdite on void-packages repository

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

Comment:
> Isn't the one at memtest.org MemTest86+? It has the same name and version numbers, and is identical in both appearance and function.

Woops sorry yes you are right.  memetest86.com is the commercial one.

@yopito I would have thought that memtest doesn't use an external libc?  I'll make a build once I have some more spare time.

Re: memtest86+: Hardlocks on systems with more than 4GB of RAM (packaging/compilation issue, upstream build works fine)

[Veyrdite]

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

New comment by Veyrdite on void-packages repository

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

Comment:
> Isn't the one at memtest.org MemTest86+? It has the same name and version numbers, and is identical in both appearance and function.

Woops sorry yes you are right.  The commercial one is memtest86.com (not to be confused with https://www.memetest.org/ )

@yopito I would have thought that memtest doesn't use an external libc?  I'll make a build once I have some more spare time.

Re: memtest86+: Hardlocks on systems with more than 4GB of RAM (packaging/compilation issue, upstream build works fine)

[leahneukirchen]

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

New comment by leahneukirchen on void-packages repository

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

Comment:
I tried Void memtest a few weeks ago with 48G ram and it froze after a few seconds too.

Re: memtest86+: Hardlocks on systems with more than 4GB of RAM (packaging/compilation issue, upstream build works fine)

[leahneukirchen]

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

New comment by leahneukirchen on void-packages repository

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

Comment:
Any good reason we just don't ship upstream binaries?

Re: memtest86+: Hardlocks on systems with more than 4GB of RAM (packaging/compilation issue, upstream build works fine)

[leahneukirchen]

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

New comment by leahneukirchen on void-packages repository

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

Comment:
Just checked this on my machine, the upstream binary works fine indeed. Unless someone is very interested in fixing the toolchain, I'd suggest to use upstream binary instead and not compile ourselves.

Re: memtest86+: Hardlocks on systems with more than 4GB of RAM (packaging/compilation issue, upstream build works fine)

[yopito]

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

New comment by yopito on void-packages repository

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

Comment:
I agree to package upstream binary instead of building from source if it works better.
I'll give a try to package it this way.

Re: memtest86+: Hardlocks on systems with more than 4GB of RAM (packaging/compilation issue, upstream build works fine)

[yopito]

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

New comment by yopito on void-packages repository

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

Comment:
package binary memtest (see PR above). Could you give a try ?

Re: memtest86+: Hardlocks on systems with more than 4GB of RAM (packaging/compilation issue, upstream build works fine)

[github-actions]

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

New comment by github-actions[bot] on void-packages repository

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

Comment:
Issues become stale 90 days after last activity and are closed 14 days after that.  If this issue is still relevant bump it or assign it.

Re: [ISSUE] [CLOSED] memtest86+: Hardlocks on systems with more than 4GB of RAM (packaging/compilation issue, upstream build works fine)

[leahneukirchen]

[-- 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)
```