Remeber: ERROR: Memory lock failed - reason unknown.

[dukebound85]

As the title says, i get that message when selecting all in rember

what does it mean?

do i have bad ram?

 

[dukebound85]

ran rember for 1 loop and this is what it resulted in

Test Results

All tests passed!

Total built-in memory: 8 GB


This is the total amount of physical memory that the computer has installed. If this figure is not showing the correct amount of memory there may be a problem with one or more installed DIMMS.

Available memory: 6955 MB

Available memory is the amount of physical memory that is currently not in use by any other processes. All available memory will be used for testing when the "All" option is selected. To increase the amount of available memory, you can restart your computer before testing. If you are familiar with the command line (CLI), you can run memtest (the core of Rember) in single-user mode. See Rember help, or http://www.memtestosx.org for more information.

Requested amount: All MB

The total amount of memory requested for testing by the Rember application. Not all requested memory can be allocated for testing. See information on "Available memory" for more information.

Memory allocated for testing: 6760 MB

This is the total amount of memory that memtest was able to allocate for testing. See "Available memory" section for more information.

-------

Loops selected: 1

Total loops selected by user for testing. All loops should complete when testing is successful. Test failure when the "Continue on Error" preference is selected will cancel tests before this number of loops has been completed. Users can also cancel testing before this number is reached.

Loops completed: 0

Total loops completed by memtest. Note that the Rember is not always able to identify how many loops ran. If there are discrepancies between this and the loops selected, the log should be examined to determine exactly how many loops were performed.
-------

Total execution time: 159 seconds

This is the total amount of time that it took to execute the selected tests. Execution time may vary from system to system, and is provided as a guide for determining how long users can expect tests to run based on the amount of memory installed on the system.

Testing start time: 2009-01-22 16:29:53 -0700

Testing end time: 2009-01-22 17:58:59 -0700

here is the log

Memtest version 4.2 (64-bit)
Copyright (C) 2004 Charles Cazabon
Copyright (C) 2004, 2005, 2006 Tony Scaminaci (Macintosh ports)
Licensed under the GNU General Public License version 2 only

Mac OS X 10.5.6 (9G55) running in single user mode
Memory Page Size: 4096
System has 4 Intel processor(s) with SSE
Requested memory: 6955MB (7293280256 bytes)
Available memory: 6955MB (7293280256 bytes)
NOTE: Memory request is too large, reducing to acceptable value...
Allocated memory: 6760MB (7089068352 bytes) at local address 0x0000000101000000
Attempting memory lock... WARNING: Testing with unlocked memory may be slower and less reliable

ERROR: Memory lock failed - reason unknown.

Partitioning memory into 2 comparison buffers...
Buffer A: 3380MB (3544534176 bytes) starts at local address 0x0000000101000000
Buffer B: 3380MB (3544534176 bytes) starts at local address 0x00000001d4454ca0

Running 1 test sequence... (CTRL-C to quit)

Test sequence 1 of 1:

Running tests on full 6760MB region...
Stuck Address : setting 1 of 16ok
Linear PRN : setting 1 of 16ok
Running comparison tests using 3380MB buffers...
Random Value : \ ok
Compare XOR :  ok
Compare SUB :  ok
Compare MUL :  ok
Compare DIV :  ok
Compare OR :  ok
Compare AND :  ok
Sequential Increment:  ok
Solid Bits : setting 1 of 64
Block Sequential : setting 1 of 256ok
Checkerboard : setting 1 of 64ok
Bit Spread : setting 1 of 128
Bit Flip : setting 1 of 512ok
Walking Ones : setting 1 of 128
Walking Zeroes : setting 1 of 64ok

All tests passed! Execution time: 5342 seconds.

I dont get why
1) the ram didnt lock
2) why it says 0 loops completed but 1 loop was selected
3) why solid bits, bit spread, and walking ones do not have an "ok" to the right of them

 

[blekenbleu]

ran rember for 1 loop
I dont get why
1) the ram didnt lock

rember invokes memtest, which may have better documentation
http://www.memtestosx.org/joomla/index.php

Ram was not locked because root permission is required for locking.
I see the same message when running e.g. memtest all 1 -L
so need to run:

sudo memtest all 1 -L

Changing permissions for root-only execution on rember
might make OSX prompt for your password and run rember as root,
but IMO it makes little sense to test memory from a GUI,
since the GUI is using appreciable memory which will be unavailable to test.

 

[create]

...
Ram was not locked because root permission is required for locking.
I see the same message when running e.g. memtest all 1 -L

Nope. The reason memtest is unable to lock the memory is because you are on a 32 bit kernel and it is trying to lock more than 4GB. To change this you will need to hold the 6 and 4 keys while booting (looks like OP was using Leopard and I believe this works with that).

Another option if yo do not want to mess with 64 bit kernel is to run multiple concurrent memtest checks for less than 4G each.