All releases of memtester
Release Notes: This release adds a progress message for one more errno value (EAGAIN) in response to failed mlock; BSDs use this to indicate the lock failed due to being over a system or process limit, much like ENOMEM.
Release Notes: A problem in which offsets/addresses were not being reported correctly in test failure messages was fixed.
Release Notes: _FILE_OFFSET_BITS is now defined as 64 bits by default in conf-cc, which causes some 32-bit systems with larger than 32-bit address spaces to have a 64-bit off_t, allowing testing of larger chunks of memory. Tests of 8 and 16-bit wide random writes were added to enable verification of the correct operation of hardware. If these tests trigger unaligned access problems on your platform, they can be eliminated by removing the -DTEST_NARROW_WRITES definition from the conf-cc file.
Release Notes: This release fixes 64-bit data patterns with some versions of gcc. It clarifies 'make install' in the readme.
Release Notes: This release fixes a portability issue with the MAP_LOCKED flag. It removes debugging output accidentally left in v.4.1.0. There are some cleanups.
Release Notes: This release improves the documentation and adds two features: one is the ability to specify the amount of memory to test more easily, and the other is to allocate a specific physical region of memory to test (primarily of interest to hardware developers).
Release Notes: This release adds a startup check for the amount of memory being greater than the possible address space. This prevents user confusion on 32-bit systems that use addressing tricks to have over 4GB total system memory. There are documentation updates.
Release Notes: A bug has been fixed in the align-to-page logic that may have prevented memtester from mlock()ing the memory it was trying to test on some systems.
Release Notes: This release improves the test algorithm; the walking 0 bits test was only walking the 0 bit in one direction, instead of walking it up and back down the line the way it was intended to.
Release Notes: Change to the method of allocating and locking memory: if EPERM is encountered when trying to mlock(), this release will reset the amount of memory desired to the original amount and try again without mlock(). The reason for this is that on many systems, mlock() won't return EPERM until after having returned ENOMEM for a larger amount. The new behaviour allows processes without mlock privileges to still test the fully-specified amount or as much memory as can be allocated.
