PINE64
Rockpro64 RAM issues - Printable Version

+- PINE64 (https://forum.pine64.org)
+-- Forum: ROCKPRO64 (https://forum.pine64.org/forumdisplay.php?fid=98)
+--- Forum: General Discussion on ROCKPRO64 (https://forum.pine64.org/forumdisplay.php?fid=99)
+--- Thread: Rockpro64 RAM issues (/showthread.php?tid=11454)



Rockpro64 RAM issues - sausal - 09-15-2020

Hi All,

What methods are you using to test memory? I have clear Debian install(not depends what distribution is used) and when the bigger size of memory is allocated with memtester and shows multiple failures.

The same not depending from power source 12v3A and 12v5A was tested:

Code:
debian@rockpro64:~/linux-build$ sudo memtester 3000M
memtester version 4.3.0 (64-bit)
Copyright (C) 2001-2012 Charles Cazabon.
Licensed under the GNU General Public License version 2 (only).

pagesize is 4096
pagesizemask is 0xfffffffffffff000
want 3000MB (3145728000 bytes)
got  3000MB (3145728000 bytes), trying mlock ...
locked.
Loop 1:
  Stuck Address       : setting   0
ok
  Random Value        : ok
  Compare XOR         : ok
  Compare SUB         : ok
  Compare MUL         : ok
FAILURE: 0x00000001 != 0x00000000 at offset 0x02b11878.
FAILURE: 0x00000002 != 0x00000003 at offset 0x02b11880.
FAILURE: 0x00000002 != 0x00000003 at offset 0x02b11888.
FAILURE: 0x00000000 != 0x100000000 at offset 0x58553c38.
FAILURE: 0x00000001 != 0x00000011 at offset 0x58553c40.
FAILURE: 0x00000002 != 0x1000000002 at offset 0x58553c48.
FAILURE: 0x00000002 != 0x1000000002 at offset 0x59654278.
FAILURE: 0x00000003 != 0x4000000003 at offset 0x59654280.
FAILURE: 0x00000001 != 0x00000005 at offset 0x59654288.
FAILURE: 0x00000001 != 0x00000000 at offset 0x597542b8.
FAILURE: 0x00000001 != 0x00000041 at offset 0x597542c0.
FAILURE: 0x00000001 != 0x00000041 at offset 0x597542c8.
FAILURE: 0x00000002 != 0x400000012 at offset 0x597544c0.
FAILURE: 0x00000003 != 0x400000013 at offset 0x597544c8.
FAILURE: 0x00000003 != 0x4000000003 at offset 0x598544b8.
FAILURE: 0x00000001 != 0x100000001 at offset 0x598544c0.
FAILURE: 0x00000000 != 0x00000040 at offset 0x598544c8.
FAILURE: 0x00000003 != 0x1000000043 at offset 0x59954088.
  Compare DIV         : FAILURE: 0x6bfc31142fff05e5 != 0x6bfc31152fff05e5 at offset 0x58553c38.
FAILURE: 0x6bfc31142fff05e5 != 0x6bfc31142fff05f5 at offset 0x58553c40.
FAILURE: 0x6bfc31142fff05e7 != 0x6bfc31542fff05e7 at offset 0x59654280.
FAILURE: 0x6bfc31142fff05e7 != 0x6bfc31142fff05e5 at offset 0x596d3e78.
FAILURE: 0x6bfc31142fff05e5 != 0x6bfc31142fff05e7 at offset 0x596d3e80.
FAILURE: 0x6bfc31142fff05e7 != 0x6bfc31142fff05f7 at offset 0x597544c0.
FAILURE: 0x6bfc31142fff05e7 != 0x6bfc31142fff05f7 at offset 0x597544c8.
FAILURE: 0x6bfc31142fff05e7 != 0x6bfc31542fff05e7 at offset 0x598544b8.
FAILURE: 0x6bfc31142fff05e5 != 0x6bfc31152fff05e5 at offset 0x598544c0.
FAILURE: 0x6bfc31142fff05e7 != 0x6bfc31142fff05e5 at offset 0x598d43f8.

Why I am testing is that Debian crashes during regular operations. Rsync is not usable including any other higher load tasks which finishes with random backtraces.


RE: Rockpro64 RAM issues - aleksei - 09-17-2020

I don't own RockPro64 but there's something about memory glitches in the wiki, does that match your symptoms?
https://wiki.pine64.org/index.php/ROCKPro64#Older_firmware_overwrites_actively_used_memory


RE: Rockpro64 RAM issues - tllim - 09-19-2020

(09-15-2020, 02:40 AM)sausal Wrote: Hi All,

What methods are you using to test memory? I have clear Debian install(not depends what distribution is used) and when the bigger size of memory is allocated with memtester and shows multiple failures.

The same not depending from power source 12v3A and 12v5A was tested:

Code:
debian@rockpro64:~/linux-build$ sudo memtester 3000M
memtester version 4.3.0 (64-bit)
Copyright (C) 2001-2012 Charles Cazabon.
Licensed under the GNU General Public License version 2 (only).

pagesize is 4096
pagesizemask is 0xfffffffffffff000
want 3000MB (3145728000 bytes)
got  3000MB (3145728000 bytes), trying mlock ...
locked.
Loop 1:
  Stuck Address       : setting   0
ok
  Random Value        : ok
  Compare XOR         : ok
  Compare SUB         : ok
  Compare MUL         : ok
FAILURE: 0x00000001 != 0x00000000 at offset 0x02b11878.
FAILURE: 0x00000002 != 0x00000003 at offset 0x02b11880.
FAILURE: 0x00000002 != 0x00000003 at offset 0x02b11888.
FAILURE: 0x00000000 != 0x100000000 at offset 0x58553c38.
FAILURE: 0x00000001 != 0x00000011 at offset 0x58553c40.
FAILURE: 0x00000002 != 0x1000000002 at offset 0x58553c48.
FAILURE: 0x00000002 != 0x1000000002 at offset 0x59654278.
FAILURE: 0x00000003 != 0x4000000003 at offset 0x59654280.
FAILURE: 0x00000001 != 0x00000005 at offset 0x59654288.
FAILURE: 0x00000001 != 0x00000000 at offset 0x597542b8.
FAILURE: 0x00000001 != 0x00000041 at offset 0x597542c0.
FAILURE: 0x00000001 != 0x00000041 at offset 0x597542c8.
FAILURE: 0x00000002 != 0x400000012 at offset 0x597544c0.
FAILURE: 0x00000003 != 0x400000013 at offset 0x597544c8.
FAILURE: 0x00000003 != 0x4000000003 at offset 0x598544b8.
FAILURE: 0x00000001 != 0x100000001 at offset 0x598544c0.
FAILURE: 0x00000000 != 0x00000040 at offset 0x598544c8.
FAILURE: 0x00000003 != 0x1000000043 at offset 0x59954088.
  Compare DIV         : FAILURE: 0x6bfc31142fff05e5 != 0x6bfc31152fff05e5 at offset 0x58553c38.
FAILURE: 0x6bfc31142fff05e5 != 0x6bfc31142fff05f5 at offset 0x58553c40.
FAILURE: 0x6bfc31142fff05e7 != 0x6bfc31542fff05e7 at offset 0x59654280.
FAILURE: 0x6bfc31142fff05e7 != 0x6bfc31142fff05e5 at offset 0x596d3e78.
FAILURE: 0x6bfc31142fff05e5 != 0x6bfc31142fff05e7 at offset 0x596d3e80.
FAILURE: 0x6bfc31142fff05e7 != 0x6bfc31142fff05f7 at offset 0x597544c0.
FAILURE: 0x6bfc31142fff05e7 != 0x6bfc31142fff05f7 at offset 0x597544c8.
FAILURE: 0x6bfc31142fff05e7 != 0x6bfc31542fff05e7 at offset 0x598544b8.
FAILURE: 0x6bfc31142fff05e5 != 0x6bfc31152fff05e5 at offset 0x598544c0.
FAILURE: 0x6bfc31142fff05e7 != 0x6bfc31142fff05e5 at offset 0x598d43f8.

Why I am testing is that Debian crashes during regular operations. Rsync is not usable including any other higher load tasks which finishes with random backtraces.

Please install meemtester and check out memory stability.
sudo apt-get install memtester
sudo memtester xxxxM

For 2GB Board xxxx = 1700
For 4GB Voaes xxxx = 3700


RE: Rockpro64 RAM issues - kop316 - 10-16-2020

(09-19-2020, 02:08 PM)tllim Wrote:
(09-15-2020, 02:40 AM)sausal Wrote: Hi All,

What methods are you using to test memory? I have clear Debian install(not depends what distribution is used) and when the bigger size of memory is allocated with memtester and shows multiple failures.

The same not depending from power source 12v3A and 12v5A was tested:

Code:
debian@rockpro64:~/linux-build$ sudo memtester 3000M
memtester version 4.3.0 (64-bit)
Copyright (C) 2001-2012 Charles Cazabon.
Licensed under the GNU General Public License version 2 (only).

pagesize is 4096
pagesizemask is 0xfffffffffffff000
want 3000MB (3145728000 bytes)
got  3000MB (3145728000 bytes), trying mlock ...
locked.
Loop 1:
  Stuck Address       : setting   0
ok
  Random Value        : ok
  Compare XOR         : ok
  Compare SUB         : ok
  Compare MUL         : ok
FAILURE: 0x00000001 != 0x00000000 at offset 0x02b11878.
FAILURE: 0x00000002 != 0x00000003 at offset 0x02b11880.
FAILURE: 0x00000002 != 0x00000003 at offset 0x02b11888.
FAILURE: 0x00000000 != 0x100000000 at offset 0x58553c38.
FAILURE: 0x00000001 != 0x00000011 at offset 0x58553c40.
FAILURE: 0x00000002 != 0x1000000002 at offset 0x58553c48.
FAILURE: 0x00000002 != 0x1000000002 at offset 0x59654278.
FAILURE: 0x00000003 != 0x4000000003 at offset 0x59654280.
FAILURE: 0x00000001 != 0x00000005 at offset 0x59654288.
FAILURE: 0x00000001 != 0x00000000 at offset 0x597542b8.
FAILURE: 0x00000001 != 0x00000041 at offset 0x597542c0.
FAILURE: 0x00000001 != 0x00000041 at offset 0x597542c8.
FAILURE: 0x00000002 != 0x400000012 at offset 0x597544c0.
FAILURE: 0x00000003 != 0x400000013 at offset 0x597544c8.
FAILURE: 0x00000003 != 0x4000000003 at offset 0x598544b8.
FAILURE: 0x00000001 != 0x100000001 at offset 0x598544c0.
FAILURE: 0x00000000 != 0x00000040 at offset 0x598544c8.
FAILURE: 0x00000003 != 0x1000000043 at offset 0x59954088.
  Compare DIV         : FAILURE: 0x6bfc31142fff05e5 != 0x6bfc31152fff05e5 at offset 0x58553c38.
FAILURE: 0x6bfc31142fff05e5 != 0x6bfc31142fff05f5 at offset 0x58553c40.
FAILURE: 0x6bfc31142fff05e7 != 0x6bfc31542fff05e7 at offset 0x59654280.
FAILURE: 0x6bfc31142fff05e7 != 0x6bfc31142fff05e5 at offset 0x596d3e78.
FAILURE: 0x6bfc31142fff05e5 != 0x6bfc31142fff05e7 at offset 0x596d3e80.
FAILURE: 0x6bfc31142fff05e7 != 0x6bfc31142fff05f7 at offset 0x597544c0.
FAILURE: 0x6bfc31142fff05e7 != 0x6bfc31142fff05f7 at offset 0x597544c8.
FAILURE: 0x6bfc31142fff05e7 != 0x6bfc31542fff05e7 at offset 0x598544b8.
FAILURE: 0x6bfc31142fff05e5 != 0x6bfc31152fff05e5 at offset 0x598544c0.
FAILURE: 0x6bfc31142fff05e7 != 0x6bfc31142fff05e5 at offset 0x598d43f8.

Why I am testing is that Debian crashes during regular operations. Rsync is not usable including any other higher load tasks which finishes with random backtraces.

Please install meemtester and check out memory stability.
sudo apt-get install memtester
sudo memtester xxxxM

For 2GB Board xxxx = 1700
For 4GB Voaes xxxx = 3700

I am having the same issues:

https://forum.pine64.org/showthread.php?tid=11714

Support at Pine is unfortunately terrible, and I had to open up a paypal dispute.


RE: Rockpro64 RAM issues - mstevens - 11-30-2020

(10-16-2020, 03:06 PM)kop316 Wrote:
(09-19-2020, 02:08 PM)tllim Wrote:
(09-15-2020, 02:40 AM)sausal Wrote: Hi All,

What methods are you using to test memory? I have clear Debian install(not depends what distribution is used) and when the bigger size of memory is allocated with memtester and shows multiple failures.

The same not depending from power source 12v3A and 12v5A was tested:

Code:
debian@rockpro64:~/linux-build$ sudo memtester 3000M
memtester version 4.3.0 (64-bit)
Copyright (C) 2001-2012 Charles Cazabon.
Licensed under the GNU General Public License version 2 (only).

pagesize is 4096
pagesizemask is 0xfffffffffffff000
want 3000MB (3145728000 bytes)
got  3000MB (3145728000 bytes), trying mlock ...
locked.
Loop 1:
  Stuck Address       : setting   0
ok
  Random Value        : ok
  Compare XOR         : ok
  Compare SUB         : ok
  Compare MUL         : ok
FAILURE: 0x00000001 != 0x00000000 at offset 0x02b11878.
FAILURE: 0x00000002 != 0x00000003 at offset 0x02b11880.
FAILURE: 0x00000002 != 0x00000003 at offset 0x02b11888.
FAILURE: 0x00000000 != 0x100000000 at offset 0x58553c38.
FAILURE: 0x00000001 != 0x00000011 at offset 0x58553c40.
FAILURE: 0x00000002 != 0x1000000002 at offset 0x58553c48.
FAILURE: 0x00000002 != 0x1000000002 at offset 0x59654278.
FAILURE: 0x00000003 != 0x4000000003 at offset 0x59654280.
FAILURE: 0x00000001 != 0x00000005 at offset 0x59654288.
FAILURE: 0x00000001 != 0x00000000 at offset 0x597542b8.
FAILURE: 0x00000001 != 0x00000041 at offset 0x597542c0.
FAILURE: 0x00000001 != 0x00000041 at offset 0x597542c8.
FAILURE: 0x00000002 != 0x400000012 at offset 0x597544c0.
FAILURE: 0x00000003 != 0x400000013 at offset 0x597544c8.
FAILURE: 0x00000003 != 0x4000000003 at offset 0x598544b8.
FAILURE: 0x00000001 != 0x100000001 at offset 0x598544c0.
FAILURE: 0x00000000 != 0x00000040 at offset 0x598544c8.
FAILURE: 0x00000003 != 0x1000000043 at offset 0x59954088.
  Compare DIV         : FAILURE: 0x6bfc31142fff05e5 != 0x6bfc31152fff05e5 at offset 0x58553c38.
FAILURE: 0x6bfc31142fff05e5 != 0x6bfc31142fff05f5 at offset 0x58553c40.
FAILURE: 0x6bfc31142fff05e7 != 0x6bfc31542fff05e7 at offset 0x59654280.
FAILURE: 0x6bfc31142fff05e7 != 0x6bfc31142fff05e5 at offset 0x596d3e78.
FAILURE: 0x6bfc31142fff05e5 != 0x6bfc31142fff05e7 at offset 0x596d3e80.
FAILURE: 0x6bfc31142fff05e7 != 0x6bfc31142fff05f7 at offset 0x597544c0.
FAILURE: 0x6bfc31142fff05e7 != 0x6bfc31142fff05f7 at offset 0x597544c8.
FAILURE: 0x6bfc31142fff05e7 != 0x6bfc31542fff05e7 at offset 0x598544b8.
FAILURE: 0x6bfc31142fff05e5 != 0x6bfc31152fff05e5 at offset 0x598544c0.
FAILURE: 0x6bfc31142fff05e7 != 0x6bfc31142fff05e5 at offset 0x598d43f8.

Why I am testing is that Debian crashes during regular operations. Rsync is not usable including any other higher load tasks which finishes with random backtraces.

Please install meemtester and check out memory stability.
sudo apt-get install memtester
sudo memtester xxxxM

For 2GB Board xxxx = 1700
For 4GB Voaes xxxx = 3700

I am having the same issues:

https://forum.pine64.org/showthread.php?tid=11714

Support at Pine is unfortunately terrible, and I had to open up a paypal dispute.

I've got similar problems, has anyone got a way to get a response from support without involving paypal? My ticket was going well at first, then I haven't had a response in over a month.


RE: Rockpro64 RAM issues - tllim - 12-06-2020

I've got similar problems, has anyone got a way to get a response from support without involving paypal? My ticket was going well at first, then I haven't had a response in over a month.

Please PM me your support ticket number and I will inform support team. Sorry on dropping this ball.