Name | memtester |
Version | 4.5.1 |
Category | misc |
Description | A userspace utility for testing the memory subsystem for faults. |
Maintainer | pascal.bellard@slitaz.org |
License | GPL2 |
Website | https://github.com/jnavila/memtester |
Tags | test diagnostic RAM |
Sizes |
Download package | |
Show receipt | |
Show files list | |
Show cooking log | |
Install package Remove package |
Description
memtester is a utility for testing the memory subsystem in a computer to determine if it is faulty. Usage is simple for the basic case. As root, run the resulting memtester binary with the following commandline:
where
An optional Note: the memory specified will be overwritten during testing; you therefore cannot specify a region belonging to the kernel or other applications without causing the other process or entire system to crash). If you use this option, it is up to you to ensure the specified memory is safe to overwrite. That makes this option mostly of use for testing memory-mapped I/O devices and similar. Thanks to Allon Stern for the idea behind this feature. For example, if you want to test a bank of RAM or device which is 64kbytes in size and starts at physical address 0x0C0000 through the normal /dev/mem, you would run memtester as follows:
If instead that device presented its memory as /dev/foodev at offset 0, you would run memtester instead as follows:
Note that the memtester must run as user root so that it can lock its pages into memory. If memtester fails to lock its pages, it will issue a warning and continue regardless. Testing without the memory being locked is generally very slow and not particularly accurate, as you'll end up testing the same memory over and over as the system swaps the larger region. |