/memtester, Utility for testing the memory subsystem for faults
4.3.0, Package name:
memtester-4.3.0, Maintainer: schmonz
memtest is a utility for testing the memory subsystem in a computer
to determine if it is faulty. The original source was by Simon
Kirby <firstname.lastname@example.org>. Charles Cazabon has by this time completely
rewritten the original source, and added many additional tests to
help catch borderline memory. He also rewrote the original tests
(which catch mainly memory bits which are stuck permanently high
or low) so that they run approximately an order of magnitude faster.
Master sites: SHA1:
Version history: (Expand)
- (2012-06-22) Updated to version: memtester-4.3.0
- (2012-01-11) Updated to version: memtester-4.2.2
- (2010-10-27) Updated to version: memtester-4.2.1
- (2010-03-04) Updated to version: memtester-4.1.3
- (2009-08-03) Updated to version: memtester-4.1.2
- (2007-12-08) Updated to version: memtester-4.0.8
CVS history: (Expand)
| 2015-11-04 02:32:42 by Alistair G. Crooks | Files touched by this commit (499) |
Add SHA512 digests for distfiles for sysutils category
Problems found with existing digests:
Package memconf distfile memconf-2.16/memconf.gz
Problems found locating distfiles:
Package dc-tools: missing distfile dc-tools/abs0-dc-burn-netbsd-1.5-0-gae55ec9
Package ipw-firmware: missing distfile ipw2100-fw-1.2.tgz
Package iwi-firmware: missing distfile ipw2200-fw-2.3.tgz
Package nvnet: missing distfile nvnet-netbsd-src-20050620.tgz
Package syslog-ng: missing distfile syslog-ng-3.7.2.tar.gz
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
| 2014-10-09 16:07:17 by Thomas Klausner | Files touched by this commit (1163) |
Remove pkgviews: don't set PKG_INSTALLATION_TYPES in Makefiles.
| 2012-10-23 21:51:39 by Aleksej Saushev | Files touched by this commit (447) |
Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.
| 2012-06-21 23:08:11 by Amitai Schlair | Files touched by this commit (2) | |
Update to 4.3.0. From the changelog:
- add ability to mmap a device other than /dev/mem, enabling easier
testing of memory for hardware engineers et al if their system's
kernel exports the memory they're interested in via /dev/mydevice
or similar. Thanks: Jean-Noel Avila.
- add ability to run only specified tests by setting the environment
variable MEMTESTER_TEST_MASK to a bitmask of the indexes of the
tests to be run. Thanks: Ian Alexander.
Updating this during the freeze as it's a leaf package and the
changes should be low-impact.
| 2012-01-11 18:01:18 by Amitai Schlair | Files touched by this commit (2) | |
Update to 4.2.2. From the changelog:
- add 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.
| 2010-10-26 22:22:04 by Zafer Aydogan | Files touched by this commit (2) | |
Update memtester to 4.2.1
3 October 2010
-fix offsets/addresses were not being reported correctly in test failure
messages. Thanks: Anton Sergeev.
30 July 2010
-define _FILE_OFFSET_BITS to 64 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. Thanks to Steven A. Falco for
the suggestion. Let me know if this definition causes problems for anyone.
-add tests of 8-bit-wide and 16-bit-wide random writes, to enable verifying
the correct operation of hardware. Thanks: Dick Hollenbeck. If these tests
trigger unaligned access problems on your platform, you can eliminate these
tests by removing the -DTEST_NARROW_WRITES definition from the conf-cc file.
| 2010-03-04 09:43:21 by Amitai Schlair | Files touched by this commit (2) | |
Update to 4.1.3. From the changelog:
-fix 64-bit data patterns with some versions of gcc. Thanks: Tony Battersby.
-clarify `make install` in readme. Thanks: Marc Lobelle.
| 2009-08-03 17:51:40 by Amitai Schlair | Files touched by this commit (2) | |
Update to 4.1.2. From the changelog:
- fix portability issue with MAP_LOCKED flag. Thanks: Scott Haneda.
- remove debugging output accidentally left in v.4.1.0.
- memtester.h was missing from the 4.1.0 tarball; release update to
fix that. Thanks: Owen Leonard.
- added the ability to test a specific physical region of memory
(by mmap'ing /dev/mem) with the new -p option, which takes a
hex starting address as a value. This is mostly of use to
developers trying to verify memory or I/O mapped devices (on
an embedded system, for instance). Thanks: Allon Stern.
- re-add the ability to set a suffix on the memory to allocate:
"3G", "128K", etc, mostly for use with the above new feature,
where the "memory" to be tested is less than a megabyte, but
also useful for users wanting to test many gigabytes; you no
longer have to do the conversion-to-megs in your head.
- documentation updates and clarifications.